Continuous anomaly detection service

ABSTRACT

An anomaly detection system includes a plurality of signals. Each of the signals is associated with an anomaly detection procedure that will be used to identify anomalies within the signal. Anomaly detection is performed by applying the anomaly detection procedure to a sequential set of data points of a signal. The signals are updated based on incoming data streams. The data streams are analyzed, and the sequential set of data points for each signal is updated based on data points extracted from the data streams.

BACKGROUND

Many organizations such as businesses, associations, and governmentsemploy complex information technology systems. Often, a system requirestens, hundreds, and even thousands of components such as web servers,application servers, databases, firewalls, routers, operating systems,and software applications. Each of these components may produce datarelating to the operation of the component. In some instances, someportion of this data may be analyzed to identify, diagnose, and remedyproblems within an information technology system. Errors messages,aberrant values, and other similar content within the produced data mayindicate that a problem is occurring, and may be monitored automaticallyand by human technicians.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 illustrates a networked computer environment in which anembodiment may be implemented;

FIG. 2 illustrates a block diagram of an example data intake and querysystem in which an embodiment may be implemented;

FIG. 3 is a flow diagram that illustrates how indexers process, index,and store data received from forwarders in accordance with the disclosedembodiments;

FIG. 4 is a flow diagram that illustrates how a search head and indexersperform a search query in accordance with the disclosed embodiments;

FIG. 5 illustrates an exemplary graphical user interface for anomalydetection in accordance with one or more embodiments of the presentdisclosure;

FIG. 6 illustrates an exemplary graphical user interface in accordancewith one or more embodiments of the present disclosure;

FIG. 7 illustrates an exemplary graphical user interface in accordancewith one or more embodiments of the present disclosure;

FIG. 8 is a flow diagram depicting exemplary steps in accordance withone or more embodiments of the present disclosure;

FIG. 9 is a block diagram depicting exemplary anomaly detection inaccordance with some embodiments of the present disclosure;

FIG. 10 is a block diagram depicting an exemplary configuration systemin accordance with some embodiments of the present disclosure;

FIG. 11 is a block diagram of an exemplary anomaly detection system inaccordance with some embodiments of the present disclosure;

FIG. 12 is a flow diagram depicting exemplary steps for setup andmodification of an anomaly detection system in accordance with someembodiments of the present disclosure; and

FIG. 13 is a flow diagram depicting exemplary steps for operating ananomaly detection system in accordance with some embodiments of thepresent disclosure.

DETAILED DESCRIPTION

In at least one embodiment, a computer-implemented method for performinganomaly detection comprises receiving a plurality of data streams andstoring, for each of the data streams, one or more events in a fieldsearchable data store. In an embodiment, the method also comprisesdetermining, for each of the data streams, whether the data streamcorresponds to one or more of a plurality of signals, identifying withineach of the data streams corresponding to the one or more of theplurality of signals a set of data points, and continuously performinganomaly detection on the identified set of data points.

In at least one embodiment, a non-transitory computer-readable storagemedium comprising instructions stored thereon, which when executed byone or more processors, cause the one or more processors to performoperations that comprise receiving a plurality of data streams andstoring, for each of the data streams, one or more events in a fieldsearchable data store. In an embodiment, the instructions also cause theone or more processors to perform operations that comprise determining,for each of the data streams, whether the data stream corresponds to oneor more of a plurality of signals, identifying within each of the datastreams corresponding to the one or more of the plurality of signals aset of data points, continuously performing anomaly detection on theidentified set of data points.

In at least one embodiment, a system for performing anomaly detectioncomprises at least one memory having instructions stored thereon atleast one processor configured to execute the instructions. In anembodiment, the instructions cause the processor to receive a pluralityof data streams, and store, for each of the data streams, one or moreevents in a field searchable data store. In an embodiment, theinstructions further cause the processor to determine, for each of thedata streams, whether the data stream corresponds to one or more of aplurality of signals, identify within each of the data streamscorresponding to the one or more of the plurality of signals a set ofdata points, and continuously perform anomaly detection on theidentified set of data points.

1.0. General Overview

In various embodiments described herein, data centers and othercomputing environments can comprise anywhere from a few host computersystems to thousands of systems configured to process data, servicerequests from remote clients, and perform numerous other computationaltasks. During operation, various components within these computingenvironments often generate significant volumes of machine-generateddata. For example, in one embodiment, machine data is generated byvarious components in the information technology (IT) environments, suchas servers, sensors, routers, mobile devices, Internet of Things (IoT)devices, etc. In at least one embodiment, machine-generated data caninclude system logs, network packet data, sensor data, applicationprogram data, error logs, stack traces, system performance data, etc. Inone embodiment, machine-generated data can also include performancedata, diagnostic information, and many other types of data that can beanalyzed to diagnose performance problems, monitor user interactions,and to derive other insights.

A number of tools are available to analyze machine data, that is,machine-generated data. In order to reduce the size of the potentiallyvast amount of machine data that may be generated, many of these toolstypically pre-process the data based on anticipated data-analysis needs.For example, pre-specified data items may be extracted from the machinedata and stored in a database to facilitate efficient retrieval andanalysis of those data items at search time. However, the rest of themachine data typically is not saved and discarded during pre-processing.As storage capacity becomes progressively cheaper and more plentiful,there are fewer incentives to discard these portions of machine data andmany reasons to retain more of the data.

This plentiful storage capacity is presently making it feasible to storemassive quantities of minimally processed machine data for laterretrieval and analysis. In general, storing minimally processed machinedata and performing analysis operations at search time can providegreater flexibility because it enables an analyst to search all of themachine data, instead of searching only a pre-specified set of dataitems. This may enable an analyst to investigate different aspects ofthe machine data that previously were unavailable for analysis.

However, analyzing and searching massive quantities of machine datapresents a number of challenges. For example, a data center, servers, ornetwork appliances may generate many different types and formats ofmachine data (e.g., system logs, network packet data (e.g., wire data,etc.), sensor data, application program data, error logs, stack traces,system performance data, operating system data, virtualization data,etc.) from thousands of different components, which can collectively bevery time-consuming to analyze. In another example, mobile devices maygenerate large amounts of information relating to data accesses,application performance, operating system performance, networkperformance, etc. There can be millions of mobile devices that reportthese types of information.

These challenges can be addressed by using an event-based data intakeand query system, such as the SPLUNK® ENTERPRISE system developed bySplunk Inc. of San Francisco, Calif. The SPLUNK® ENTERPRISE system isthe leading platform for providing real-time operational intelligencethat enables organizations to collect, index, and searchmachine-generated data from various websites, applications, servers,networks, and mobile devices that power their businesses. The SPLUNK®ENTERPRISE system is particularly useful for analyzing data which iscommonly found in system log files, network data, and other data inputsources. Although many of the techniques described herein are explainedwith reference to a data intake and query system similar to the SPLUNK®ENTERPRISE system, these techniques are also applicable to other typesof data systems.

In the SPLUNK® ENTERPRISE system, machine-generated data are collectedand stored as “events”. An event comprises a portion of themachine-generated data and is associated with a specific point in time.For example, events may be derived from “time series data,” where thetime series data comprises a sequence of data points (e.g., performancemeasurements from a computer system, etc.) that are associated withsuccessive points in time. In general, each event can be associated witha timestamp that is derived from the raw data in the event, determinedthrough interpolation between temporally proximate events having knowntimestamps, or determined based on other configurable rules forassociating timestamps with events, etc.

In some instances, machine data can have a predefined format, where dataitems with specific data formats are stored at predefined locations inthe data. For example, the machine data may include data stored asfields in a database table. In other instances, machine data may nothave a predefined format, that is, the data is not at fixed, predefinedlocations, but the data does have repeatable patterns and is not random.This means that some machine data can comprise various data items ofdifferent data types and that may be stored at different locationswithin the data. For example, when the data source is an operatingsystem log, an event can include one or more lines from the operatingsystem log containing raw data that includes different types ofperformance and diagnostic information associated with a specific pointin time.

Examples of components which may generate machine data from which eventscan be derived include, but are not limited to, web servers, applicationservers, databases, firewalls, routers, operating systems, and softwareapplications that execute on computer systems, mobile devices, sensors,Internet of Things (IoT) devices, etc. The data generated by such datasources can include, for example and without limitation, server logfiles, activity log files, configuration files, messages, network packetdata, performance measurements, sensor measurements, etc.

The SPLUNK® ENTERPRISE system uses flexible schema to specify how toextract information from the event data. A flexible schema may bedeveloped and redefined as needed. Note that a flexible schema may beapplied to event data “on the fly,” when it is needed (e.g., at searchtime, index time, ingestion time, etc.). When the schema is not appliedto event data until search time it may be referred to as a “late-bindingschema.”

During operation, the SPLUNK® ENTERPRISE system starts with raw inputdata (e.g., one or more system logs, streams of network packet data,sensor data, application program data, error logs, stack traces, systemperformance data, etc.). The system divides this raw data into blocks(e.g., buckets of data, each associated with a specific time frame,etc.), and parses the raw data to produce timestamped events. The systemstores the timestamped events in a data store. The system enables usersto run queries against the stored data to, for example, retrieve eventsthat meet criteria specified in a query, such as containing certainkeywords or having specific values in defined fields. As used hereinthroughout, data that is part of an event is referred to as “eventdata”. In this context, the term “field” refers to a location in theevent data containing one or more values for a specific data item. Aswill be described in more detail herein, the fields are defined byextraction rules (e.g., regular expressions) that derive one or morevalues from the portion of raw machine data in each event that has aparticular field specified by an extraction rule. The set of values soproduced are semantically-related (such as IP address), even though theraw machine data in each event may be in different formats (e.g.,semantically-related values may be in different positions in the eventsderived from different sources).

As noted above, the SPLUNK® ENTERPRISE system utilizes a late-bindingschema to event data while performing queries on events. One aspect of alate-binding schema is applying “extraction rules” to event data toextract values for specific fields during search time. Morespecifically, the extraction rules for a field can include one or moreinstructions that specify how to extract a value for the field from theevent data. An extraction rule can generally include any type ofinstruction for extracting values from data in events. In some cases, anextraction rule comprises a regular expression where a sequence ofcharacters form a search pattern, in which case the rule is referred toas a “regex rule.” The system applies the regex rule to the event datato extract values for associated fields in the event data by searchingthe event data for the sequence of characters defined in the regex rule.

In the SPLUNK® ENTERPRISE system, a field extractor may be configured toautomatically generate extraction rules for certain field values in theevents when the events are being created, indexed, or stored, orpossibly at a later time. Alternatively, a user may manually defineextraction rules for fields using a variety of techniques. In contrastto a conventional schema for a database system, a late-binding schema isnot defined at data ingestion time. Instead, the late-binding schema canbe developed on an ongoing basis until the time a query is actuallyexecuted. This means that extraction rules for the fields in a query maybe provided in the query itself, or may be located during execution ofthe query. Hence, as a user learns more about the data in the events,the user can continue to refine the late-binding schema by adding newfields, deleting fields, or modifying the field extraction rules for usethe next time the schema is used by the system. Because the SPLUNK®ENTERPRISE system maintains the underlying raw data and useslate-binding schema for searching the raw data, it enables a user tocontinue investigating and learn valuable insights about the raw data.

In some embodiments, a common field name may be used to reference two ormore fields containing equivalent data items, even though the fields maybe associated with different types of events that possibly havedifferent data formats and different extraction rules. By enabling acommon field name to be used to identify equivalent fields fromdifferent types of events generated by disparate data sources, thesystem facilitates use of a “common information model” (CIM) across thedisparate data sources.

2.0. Operating Environment

FIG. 1 illustrates a networked computer system 100 in which anembodiment may be implemented. Those skilled in the art would understandthat FIG. 1 represents one example of a networked computer system andother embodiments may use different arrangements.

The networked computer system 100 comprises one or more computingdevices. These one or more computing devices comprise any combination ofhardware and software configured to implement the various logicalcomponents described herein. For example, the one or more computingdevices may include one or more memories that store instructions forimplementing the various components described herein, one or morehardware processors configured to execute the instructions stored in theone or more memories, and various data repositories in the one or morememories for storing data structures utilized and manipulated by thevarious components.

In an embodiment, one or more client devices 102 are coupled to one ormore host devices 106 and a data intake and query system 108 via one ormore networks 104. Networks 104 broadly represent one or more LANs,WANs, cellular networks (e.g., LTE, HSPA, 3G, and other cellulartechnologies), and/or networks using any of wired, wireless, terrestrialmicrowave, or satellite links, and may include the public Internet.

2.1. Host Devices

In the illustrated embodiment, a system 100 includes one or more hostdevices 106. Host devices 106 may broadly include any number ofcomputers, virtual machine instances, and/or data centers that areconfigured to host or execute one or more instances of host applications114. In general, a host device 106 may be involved, directly orindirectly, in processing requests received from client devices 102.Each host device 106 may comprise, for example, one or more of a networkdevice, a web server, an application server, a database server, etc. Acollection of host devices 106 may be configured to implement anetwork-based service. For example, a provider of a network-basedservice may configure one or more host devices 106 and host applications114 (e.g., one or more web servers, application servers, databaseservers, etc.) to collectively implement the network-based application.

In general, client devices 102 communicate with one or more hostapplications 114 to exchange information. The communication between aclient device 102 and a host application 114 may, for example, be basedon the Hypertext Transfer Protocol (HTTP) or any other network protocol.Content delivered from the host application 114 to a client device 102may include, for example, HTML documents, media content, etc. Thecommunication between a client device 102 and host application 114 mayinclude sending various requests and receiving data packets. Forexample, in general, a client device 102 or application running on aclient device may initiate communication with a host application 114 bymaking a request for a specific resource (e.g., based on an HTTPrequest), and the application server may respond with the requestedcontent stored in one or more response packets.

In the illustrated embodiment, one or more of host applications 114 maygenerate various types of performance data during operation, includingevent logs, network data, sensor data, and other types ofmachine-generated data. For example, a host application 114 comprising aweb server may generate one or more web server logs in which details ofinteractions between the web server and any number of client devices 102is recorded. As another example, a host device 106 comprising a routermay generate one or more router logs that record information related tonetwork traffic managed by the router. As yet another example, a hostapplication 114 comprising a database server may generate one or morelogs that record information related to requests sent from other hostapplications 114 (e.g., web servers or application servers) for datamanaged by the database server.

2.2. Client Devices

Client devices 102 of FIG. 1 represent any computing device capable ofinteracting with one or more host devices 106 via a network 104.Examples of client devices 102 may include, without limitation, smartphones, tablet computers, handheld computers, wearable devices, laptopcomputers, desktop computers, servers, portable media players, gamingdevices, and so forth. In general, a client device 102 can provideaccess to different content, for instance, content provided by one ormore host devices 106, etc. Each client device 102 may comprise one ormore client applications 110, described in more detail in a separatesection hereinafter.

2.3. Client Device Applications

In an embodiment, each client device 102 may host or execute one or moreclient applications 110 that are capable of interacting with one or morehost devices 106 via one or more networks 104. For instance, a clientapplication 110 may be or comprise a web browser that a user may use tonavigate to one or more websites or other resources provided by one ormore host devices 106. As another example, a client application 110 maycomprise a mobile application or “app.” For example, an operator of anetwork-based service hosted by one or more host devices 106 may makeavailable one or more mobile apps that enable users of client devices102 to access various resources of the network-based service. As yetanother example, client applications 110 may include backgroundprocesses that perform various operations without direct interactionfrom a user. A client application 110 may include a “plug-in” or“extension” to another application, such as a web browser plug-in orextension.

In an embodiment, a client application 110 may include a monitoringcomponent 112. At a high level, the monitoring component 112 comprises asoftware component or other logic that facilitates generatingperformance data related to a client device's operating state, includingmonitoring network traffic sent and received from the client device andcollecting other device and/or application-specific information.Monitoring component 112 may be an integrated component of a clientapplication 110, a plug-in, an extension, or any other type of add-oncomponent. Monitoring component 112 may also be a stand-alone process.

In one embodiment, a monitoring component 112 may be created when aclient application 110 is developed, for example, by an applicationdeveloper using a software development kit (SDK). The SDK may includecustom monitoring code that can be incorporated into the codeimplementing a client application 110. When the code is converted to anexecutable application, the custom code implementing the monitoringfunctionality can become part of the application itself.

In some cases, an SDK or other code for implementing the monitoringfunctionality may be offered by a provider of a data intake and querysystem, such as a system 108. In such cases, the provider of the system108 can implement the custom code so that performance data generated bythe monitoring functionality is sent to the system 108 to facilitateanalysis of the performance data by a developer of the clientapplication or other users.

In an embodiment, the custom monitoring code may be incorporated intothe code of a client application 110 in a number of different ways, suchas the insertion of one or more lines in the client application codethat call or otherwise invoke the monitoring component 112. As such, adeveloper of a client application 110 can add one or more lines of codeinto the client application 110 to trigger the monitoring component 112at desired points during execution of the application. Code thattriggers the monitoring component may be referred to as a monitortrigger. For instance, a monitor trigger may be included at or near thebeginning of the executable code of the client application 110 such thatthe monitoring component 112 is initiated or triggered as theapplication is launched, or included at other points in the code thatcorrespond to various actions of the client application, such as sendinga network request or displaying a particular interface.

In an embodiment, the monitoring component 112 may monitor one or moreaspects of network traffic sent and/or received by a client application110. For example, the monitoring component 112 may be configured tomonitor data packets transmitted to and/or from one or more hostapplications 114. Incoming and/or outgoing data packets can be read orexamined to identify network data contained within the packets, forexample, and other aspects of data packets can be analyzed to determinea number of network performance statistics. Monitoring network trafficmay enable information to be gathered particular to the networkperformance associated with a client application 110 or set ofapplications.

In an embodiment, network performance data refers to any type of datathat indicates information about the network and/or network performance.Network performance data may include, for instance, a URL requested, aconnection type (e.g., HTTP, HTTPS, etc.), a connection start time, aconnection end time, an HTTP status code, request length, responselength, request headers, response headers, connection status (e.g.,completion, response time(s), failure, etc.), and the like. Uponobtaining network performance data indicating performance of thenetwork, the network performance data can be transmitted to a dataintake and query system 108 for analysis.

Upon developing a client application 110 that incorporates a monitoringcomponent 112, the client application 110 can be distributed to clientdevices 102. Applications generally can be distributed to client devices102 in any manner, or they can be pre-loaded. In some cases, theapplication may be distributed to a client device 102 via an applicationmarketplace or other application distribution system. For instance, anapplication marketplace or other application distribution system mightdistribute the application to a client device based on a request fromthe client device to download the application.

In an embodiment, the monitoring component 112 may also monitor andcollect performance data related to one or more aspects of theoperational state of a client application 110 and/or client device 102.For example, a monitoring component 112 may be configured to collectdevice performance information by monitoring one or more client deviceoperations, or by making calls to an operating system and/or one or moreother applications executing on a client device 102 for performanceinformation. Device performance information may include, for instance, acurrent wireless signal strength of the device, a current connectiontype and network carrier, current memory performance information, ageographic location of the device, a device orientation, and any otherinformation related to the operational state of the client device.

In an embodiment, the monitoring component 112 may also monitor andcollect other device profile information including, for example, a typeof client device, a manufacturer and model of the device, versions ofvarious software applications installed on the device, and so forth.

In general, a monitoring component 112 may be configured to generateperformance data in response to a monitor trigger in the code of aclient application 110 or other triggering application event, asdescribed above, and to store the performance data in one or more datarecords. Each data record, for example, may include a collection offield-value pairs, each field-value pair storing a particular item ofperformance data in association with a field for the item. For example,a data record generated by a monitoring component 112 may include a“networkLatency” field (not shown in the Figure) in which a value isstored. This field indicates a network latency measurement associatedwith one or more network requests. The data record may include a “state”field to store a value indicating a state of a network connection, andso forth for any number of aspects of collected performance data.

2.4. Data Server System

FIG. 2 depicts a block diagram of an exemplary data intake and querysystem 108, similar to the SPLUNK® ENTERPRISE system. System 108includes one or more forwarders 204 that receive data from a variety ofinput data sources 202, and one or more indexers 206 that process andstore the data in one or more data stores 208. These forwarders andindexers can comprise separate computer systems, or may alternativelycomprise separate processes executing on one or more computer systems.

Each data source 202 broadly represents a distinct source of data thatcan be consumed by a system 108. Examples of a data source 202 include,without limitation, data files, directories of files, data sent over anetwork, event logs, registries, etc.

During operation, the forwarders 204 identify which indexers 206 receivedata collected from a data source 202 and forward the data to theappropriate indexers. Forwarders 204 can also perform operations on thedata before forwarding, including removing extraneous data, detectingtimestamps in the data, parsing data, indexing data, routing data basedon criteria relating to the data being routed, and/or performing otherdata transformations.

In an embodiment, a forwarder 204 may comprise a service accessible toclient devices 102 and host devices 106 via a network 104. For example,one type of forwarder 204 may be capable of consuming vast amounts ofreal-time data from a potentially large number of client devices 102and/or host devices 106. The forwarder 204 may, for example, comprise acomputing device which implements multiple data pipelines or “queues” tohandle forwarding of network data to indexers 206. A forwarder 204 mayalso perform many of the functions that are performed by an indexer. Forexample, a forwarder 204 may perform keyword extractions on raw data orparse raw data to create events. A forwarder 204 may generate timestamps for events. Additionally or alternatively, a forwarder 204 mayperform routing of events to indexers. Data store 208 may contain eventsderived from machine data from a variety of sources all pertaining tothe same component in an IT environment, and this data may be producedby the machine in question or by other components in the IT environment.

2.5. Data Ingestion

FIG. 3 depicts a flow chart illustrating an example data flow performedby Data Intake and Query system 108, in accordance with the disclosedembodiments. The data flow illustrated in FIG. 3 is provided forillustrative purposes only; those skilled in the art would understandthat one or more of the steps of the processes illustrated in FIG. 3 maybe removed or the ordering of the steps may be changed. Furthermore, forthe purposes of illustrating a clear example, one or more particularsystem components are described in the context of performing variousoperations during each of the data flow stages. For example, a forwarderis described as receiving and processing data during an input phase; anindexer is described as parsing and indexing data during parsing andindexing phases; and a search head is described as performing a searchquery during a search phase. However, other system arrangements anddistributions of the processing steps across system components may beused.

2.5.1. Input

At block 302, a forwarder receives data from an input source, such as adata source 202 shown in FIG. 2. A forwarder initially may receive thedata as a raw data stream generated by the input source. For example, aforwarder may receive a data stream from a log file generated by anapplication server, from a stream of network data from a network device,or from any other source of data. In one embodiment, a forwarderreceives the raw data and may segment the data stream into “blocks”, or“buckets,” possibly of a uniform data size, to facilitate subsequentprocessing steps.

At block 304, a forwarder or other system component annotates each blockgenerated from the raw data with one or more metadata fields. Thesemetadata fields may, for example, provide information related to thedata block as a whole and may apply to each event that is subsequentlyderived from the data in the data block. For example, the metadatafields may include separate fields specifying each of a host, a source,and a source type related to the data block. A host field may contain avalue identifying a host name or IP address of a device that generatedthe data. A source field may contain a value identifying a source of thedata, such as a pathname of a file or a protocol and port related toreceived network data. A source type field may contain a valuespecifying a particular source type label for the data. Additionalmetadata fields may also be included during the input phase, such as acharacter encoding of the data, if known, and possibly other values thatprovide information relevant to later processing steps. In anembodiment, a forwarder forwards the annotated data blocks to anothersystem component (typically an indexer) for further processing.

The SPLUNK® ENTERPRISE system allows forwarding of data from one SPLUNK®ENTERPRISE instance to another, or even to a third-party system. SPLUNK®ENTERPRISE system can employ different types of forwarders in aconfiguration.

In an embodiment, a forwarder may contain the essential componentsneeded to forward data. It can gather data from a variety of inputs andforward the data to a SPLUNK® ENTERPRISE server for indexing andsearching. It also can tag metadata (e.g., source, source type, host,etc.).

Additionally or optionally, in an embodiment, a forwarder has thecapabilities of the aforementioned forwarder as well as additionalcapabilities. The forwarder can parse data before forwarding the data(e.g., associate a time stamp with a portion of data and create anevent, etc.) and can route data based on criteria such as source or typeof event. It can also index data locally while forwarding the data toanother indexer.

2.5.2. Parsing

At block 306, an indexer receives data blocks from a forwarder andparses the data to organize the data into events. In an embodiment, toorganize the data into events, an indexer may determine a source typeassociated with each data block (e.g., by extracting a source type labelfrom the metadata fields associated with the data block, etc.) and referto a source type configuration corresponding to the identified sourcetype. The source type definition may include one or more properties thatindicate to the indexer to automatically determine the boundaries ofevents within the data. In general, these properties may include regularexpression-based rules or delimiter rules where, for example, eventboundaries may be indicated by predefined characters or characterstrings. These predefined characters may include punctuation marks orother special characters including, for example, carriage returns, tabs,spaces, line breaks, etc. If a source type for the data is unknown tothe indexer, an indexer may infer a source type for the data byexamining the structure of the data. Then, it can apply an inferredsource type definition to the data to create the events.

At block 308, the indexer determines a timestamp for each event. Similarto the process for creating events, an indexer may again refer to asource type definition associated with the data to locate one or moreproperties that indicate instructions for determining a timestamp foreach event. The properties may, for example, instruct an indexer toextract a time value from a portion of data in the event, to interpolatetime values based on timestamps associated with temporally proximateevents, to create a timestamp based on a time the event data wasreceived or generated, to use the timestamp of a previous event, or useany other rules for determining timestamps.

At block 310, the indexer associates with each event one or moremetadata fields including a field containing the timestamp (in someembodiments, a timestamp may be included in the metadata fields)determined for the event. These metadata fields may include a number of“default fields” that are associated with all events, and may alsoinclude one more custom fields as defined by a user. Similar to themetadata fields associated with the data blocks at block 304, thedefault metadata fields associated with each event may include a host,source, and source type field including or in addition to a fieldstoring the timestamp.

At block 312, an indexer may optionally apply one or moretransformations to data included in the events created at block 306. Forexample, such transformations can include removing a portion of an event(e.g., a portion used to define event boundaries, extraneous charactersfrom the event, other extraneous text, etc.), masking a portion of anevent (e.g., masking a credit card number), removing redundant portionsof an event, etc. The transformations applied to event data may, forexample, be specified in one or more configuration files and referencedby one or more source type definitions.

2.5.3. Indexing

At blocks 314 and 316, an indexer can optionally generate a keywordindex to facilitate fast keyword searching for event data. To build akeyword index, at block 314, the indexer identifies a set of keywords ineach event. At block 316, the indexer includes the identified keywordsin an index, which associates each stored keyword with referencepointers to events containing that keyword (or to locations withinevents where that keyword is located, other location identifiers, etc.).When an indexer subsequently receives a keyword-based query, the indexercan access the keyword index to quickly identify events containing thekeyword.

In some embodiments, the keyword index may include entries forname-value pairs found in events, where a name-value pair can include apair of keywords connected by a symbol, such as an equals sign or colon.This way, events containing these name-value pairs can be quicklylocated. In some embodiments, fields can automatically be generated forsome or all of the name-value pairs at the time of indexing. Forexample, if the string “dest=10.0.1.2” is found in an event, a fieldnamed “dest” may be created for the event, and assigned a value of“10.0.1.2”.

At block 318, the indexer stores the events with an associated timestampin a data store 208. Timestamps enable a user to search for events basedon a time range. In one embodiment, the stored events are organized into“buckets,” where each bucket stores events associated with a specifictime range based on the timestamps associated with each event. This maynot only improve time-based searching, but also allows for events withrecent timestamps, which may have a higher likelihood of being accessed,to be stored in a faster memory to facilitate faster retrieval. Forexample, buckets containing the most recent events can be stored inflash memory rather than on a hard disk.

Each indexer 206 may be responsible for storing and searching a subsetof the events contained in a corresponding data store 208. Bydistributing events among the indexers and data stores, the indexers cananalyze events for a query in parallel. For example, using map-reducetechniques, each indexer returns partial responses for a subset ofevents to a search head that combines the results to produce an answerfor the query. By storing events in buckets for specific time ranges, anindexer may further optimize data retrieval process by searching bucketscorresponding to time ranges that are relevant to a query.

2.6. Query Processing

FIG. 4 is a flow diagram that illustrates an exemplary process that asearch head and one or more indexers may perform during a search query.At block 402, a search head receives a search query from a client. Atblock 404, the search head analyzes the search query to determine whatportion(s) of the query can be delegated to indexers and what portionsof the query can be executed locally by the search head. At block 406,the search head distributes the determined portions of the query to theappropriate indexers. In an embodiment, a search head cluster may takethe place of an independent search head where each search head in thesearch head cluster coordinates with peer search heads in the searchhead cluster to schedule jobs, replicate search results, updateconfigurations, fulfill search requests, etc. In an embodiment, thesearch head (or each search head) communicates with a master node (alsoknown as a cluster master, not shown in Fig.) that provides the searchhead with a list of indexers to which the search head can distribute thedetermined portions of the query. The master node maintains a list ofactive indexers and can also designate which indexers may haveresponsibility for responding to queries over certain sets of events. Asearch head may communicate with the master node before the search headdistributes queries to indexers to discover the addresses of activeindexers.

At block 408, the indexers to which the query was distributed, searchdata stores associated with them for events that are responsive to thequery. To determine which events are responsive to the query, theindexer searches for events that match the criteria specified in thequery. These criteria can include matching keywords or specific valuesfor certain fields. The searching operations at block 408 may use thelate-binding schema to extract values for specified fields from eventsat the time the query is processed. In an embodiment, one or more rulesfor extracting field values may be specified as part of a source typedefinition. The indexers may then either send the relevant events backto the search head, or use the events to determine a partial result, andsend the partial result back to the search head.

At block 410, the search head combines the partial results and/or eventsreceived from the indexers to produce a final result for the query. Thisfinal result may comprise different types of data depending on what thequery requested. For example, the results can include a listing ofmatching events returned by the query, or some type of visualization ofthe data from the returned events. In another example, the final resultcan include one or more calculated values derived from the matchingevents.

The results generated by the system 108 can be returned to a clientusing different techniques. For example, one technique streams resultsor relevant events back to a client in real-time as they are identified.Another technique waits to report the results to the client until acomplete set of results (which may include a set of relevant events or aresult based on relevant events) is ready to return to the client. Yetanother technique streams interim results or relevant events back to theclient in real-time until a complete set of results is ready, and thenreturns the complete set of results to the client. In another technique,certain results are stored as “search jobs” and the client may retrievethe results by referring the search jobs.

The search head can also perform various operations to make the searchmore efficient. For example, before the search head begins execution ofa query, the search head can determine a time range for the query and aset of common keywords that all matching events include. The search headmay then use these parameters to query the indexers to obtain a supersetof the eventual results. Then, during a filtering stage, the search headcan perform field-extraction operations on the superset to produce areduced set of search results. This speeds up queries that are performedon a periodic basis.

2.7. Field Extraction

The search head 210 allows users to search and visualize event dataextracted from raw machine data received from homogenous data sources.It also allows users to search and visualize event data extracted fromraw machine data received from heterogeneous data sources. The searchhead 210 includes various mechanisms, which may additionally reside inan indexer 206, for processing a query. Splunk Processing Language(SPL), used in conjunction with the SPLUNK® ENTERPRISE system, can beutilized to make a query. SPL is a pipelined search language in which aset of inputs is operated on by a first command in a command line, andthen a subsequent command following the pipe symbol “|” operates on theresults produced by the first command, and so on for additionalcommands. Other query languages, such as the Structured Query Language(“SQL”), can be used to create a query.

In response to receiving the search query, search head 210 usesextraction rules to extract values for the fields associated with afield or fields in the event data being searched. The search head 210obtains extraction rules that specify how to extract a value for certainfields from an event. Extraction rules can comprise regex rules thatspecify how to extract values for the relevant fields. In addition tospecifying how to extract field values, the extraction rules may alsoinclude instructions for deriving a field value by performing a functionon a character string or value retrieved by the extraction rule. Forexample, a transformation rule may truncate a character string, orconvert the character string into a different data format. In somecases, the query itself can specify one or more extraction rules.

The search head 210 can apply the extraction rules to event data that itreceives from indexers 206. Indexers 206 may apply the extraction rulesto events in an associated data store 208. Extraction rules can beapplied to all the events in a data store, or to a subset of the eventsthat have been filtered based on some criteria (e.g., event time stampvalues, etc.). Extraction rules can be used to extract one or morevalues for a field from events by parsing the event data and examiningthe event data for one or more patterns of characters, numbers,delimiters, etc., that indicate where the field begins and, optionally,ends.

3.0. It Service Monitoring

As previously mentioned, the SPLUNK® ENTERPRISE platform providesvarious schemas, dashboards and visualizations that make it easy fordevelopers to create applications to provide additional capabilities.One such application is SPLUNK® IT SERVICE INTELLIGENCE™, which performsmonitoring and alerting operations. It also includes analytics to helpan analyst diagnose the root cause of performance problems based onlarge volumes of data stored by the SPLUNK® ENTERPRISE system ascorrelated to the various services an IT organization provides (aservice-centric view). This differs significantly from conventional ITmonitoring systems that lack the infrastructure to effectively store andanalyze large volumes of service-related event data. Traditional servicemonitoring systems typically use fixed schemas to extract data frompre-defined fields at data ingestion time, wherein the extracted data istypically stored in a relational database. This data extraction processand associated reduction in data content that occurs at data ingestiontime inevitably hampers future investigations, when all of the originaldata may be needed to determine the root cause of or contributingfactors to a service issue.

In contrast, a SPLUNK® IT SERVICE INTELLIGENCE™ system stores largevolumes of minimally-processed service-related data at ingestion timefor later retrieval and analysis at search time, to perform regularmonitoring, or to investigate a service issue. To facilitate this dataretrieval process, SPLUNK® IT SERVICE INTELLIGENCE™ enables a user todefine an IT operations infrastructure from the perspective of theservices it provides. In this service-centric approach, a service suchas corporate e-mail may be defined in terms of the entities employed toprovide the service, such as host machines and network devices. Eachentity is defined to include information for identifying all of theevent data that pertains to the entity, whether produced by the entityitself or by another machine, and considering the many various ways theentity may be identified in raw machine data (such as by a URL, an IPaddress, or machine name). The service and entity definitions canorganize event data around a service so that all of the event datapertaining to that service can be easily identified. This capabilityprovides a foundation for the implementation of Key PerformanceIndicators.

One or more Key Performance Indicators (KPI's) are defined for a servicewithin the SPLUNK® IT SERVICE INTELLIGENCE™ application. Each KPImeasures an aspect of service performance at a point in time or over aperiod of time (aspect KPI's). Each KPI is defined by a search querythat derives a KPI value from the machine data of events associated withthe entities that provide the service. Information in the entitydefinitions may be used to identify the appropriate events at the time aKPI is defined or whenever a KPI value is being determined. The KPIvalues derived over time may be stored to build a valuable repository ofcurrent and historical performance information for the service, and therepository, itself, may be subject to search query processing. AggregateKPIs may be defined to provide a measure of service performancecalculated from a set of service aspect KPI values; this aggregate mayeven be taken across defined timeframes and/or across multiple services.A particular service may have an aggregate KPI derived fromsubstantially all of the aspect KPI's of the service to indicate anoverall health score for the service.

SPLUNK® IT SERVICE INTELLIGENCE™ facilitates the production ofmeaningful aggregate KPI's through a system of KPI thresholds and statevalues. Different KPI definitions may produce values in differentranges, and so the same value may mean something very different from oneKPI definition to another. To address this, SPLUNK® IT SERVICEINTELLIGENCE™ implements a translation of individual KPI values to acommon domain of “state” values. For example, a KPI range of values maybe 1-100, or 50-275, while values in the state domain may be ‘critical,’‘warning,’ ‘normal,’ and ‘informational’. Thresholds associated with aparticular KPI definition determine ranges of values for that KPI thatcorrespond to the various state values. In one case, KPI values 95-100may be set to correspond to ‘critical’ in the state domain. KPI valuesfrom disparate KPI's can be processed uniformly once they are translatedinto the common state values using the thresholds. For example, “normal80% of the time” can be applied across various KPI's. To providemeaningful aggregate KPI's, a weighting value can be assigned to eachKPI so that its influence on the calculated aggregate KPI value isincreased or decreased relative to the other KPI's.

One service in an IT environment often impacts, or is impacted by,another service. SPLUNK® IT SERVICE INTELLIGENCE™ can reflect thesedependencies. For example, a dependency relationship between a corporatee-mail service and a centralized authentication service can be reflectedby recording an association between their respective servicedefinitions. The recorded associations establish a service dependencytopology that informs the data or selection options presented in a GUI,for example. (The service dependency topology is like a “map” showinghow services are connected based on their dependencies.) The servicetopology may itself be depicted in a GUI and may be interactive to allownavigation among related services.

Entity definitions in SPLUNK® IT SERVICE INTELLIGENCE™ can includeinformational fields that can serve as metadata, implied data fields, orattributed data fields for the events identified by other aspects of theentity definition. Entity definitions in SPLUNK® IT SERVICEINTELLIGENCE™ can also be created and updated by an import of tabulardata (as represented in a CSV, another delimited file, or a search queryresult set). The import may be GUI-mediated or processed using importparameters from a GUI-based import definition process. Entitydefinitions in SPLUNK® IT SERVICE INTELLIGENCE™ can also be associatedwith a service by means of a service definition rule. Processing therule results in the matching entity definitions being associated withthe service definition. The rule can be processed at creation time, andthereafter on a scheduled or on-demand basis. This allows dynamic,rule-based updates to the service definition.

During operation, SPLUNK® IT SERVICE INTELLIGENCE™ can recognizeso-called “notable events” that may indicate a service performanceproblem or other situation of interest. These notable events can berecognized by a “correlation search” specifying trigger criteria for anotable event: every time KPI values satisfy the criteria, theapplication indicates a notable event. A severity level for the notableevent may also be specified. Furthermore, when trigger criteria aresatisfied, the correlation search may additionally or alternativelycause a service ticket to be created in an IT service management (ITSM)system, such as a systems available from ServiceNow, Inc., of SantaClara, Calif.

SPLUNK® IT SERVICE INTELLIGENCE™ provides various visualizations builton its service-centric organization of event data and the KPI valuesgenerated and collected. Visualizations can be particularly useful formonitoring or investigating service performance. SPLUNK® IT SERVICEINTELLIGENCE™ provides a service monitoring interface suitable as thehome page for ongoing IT service monitoring. The interface isappropriate for settings such as desktop use or for a wall-mounteddisplay in a network operations center (NOC). The interface mayprominently display a services health section with tiles for theaggregate KPI's indicating overall health for defined services and ageneral KPI section with tiles for KPI's related to individual serviceaspects. These tiles may display KPI information in a variety of ways,such as by being colored and ordered according to factors like the KPIstate value. They also can be interactive and navigate to visualizationsof more detailed KPI information.

SPLUNK® IT SERVICE INTELLIGENCE™ provides a service-monitoring dashboardvisualization based on a user-defined template. The template can includeuser-selectable widgets of varying types and styles to display KPIinformation. The content and the appearance of widgets can responddynamically to changing KPI information. The KPI widgets can appear inconjunction with a background image, user drawing objects, or othervisual elements, that depict the IT operations environment, for example.The KPI widgets or other GUI elements can be interactive so as toprovide navigation to visualizations of more detailed KPI information.

SPLUNK® IT SERVICE INTELLIGENCE™ provides a visualization showingdetailed time-series information for multiple KPI's in parallel graphlanes. The length of each lane can correspond to a uniform time range,while the width of each lane may be automatically adjusted to fit thedisplayed KPI data. Data within each lane may be displayed in a userselectable style, such as a line, area, or bar chart. During operation auser may select a position in the time range of the graph lanes toactivate lane inspection at that point in time. Lane inspection maydisplay an indicator for the selected time across the graph lanes anddisplay the KPI value associated with that point in time for each of thegraph lanes. The visualization may also provide navigation to aninterface for defining a correlation search, using information from thevisualization to pre-populate the definition.

SPLUNK® IT SERVICE INTELLIGENCE™ provides a visualization for incidentreview showing detailed information for notable events. The incidentreview visualization may also show summary information for the notableevents over a time frame, such as an indication of the number of notableevents at each of a number of severity levels. The severity leveldisplay may be presented as a rainbow chart with the warmest colorassociated with the highest severity classification. The incident reviewvisualization may also show summary information for the notable eventsover a time frame, such as the number of notable events occurring withinsegments of the time frame. The incident review visualization maydisplay a list of notable events within the time frame ordered by anynumber of factors, such as time or severity. The selection of aparticular notable event from the list may display detailed informationabout that notable event, including an identification of the correlationsearch that generated the notable event.

SPLUNK® IT SERVICE INTELLIGENCE™ provides pre-specified schemas forextracting relevant values from the different types of service-relatedevent data. It also enables a user to define such schemas.

3.1. Anomaly Detection

In some embodiments, anomaly detection may be a feature incorporatedinto technologies described herein and may enable users (e.g., ITmanagers operating a system such as SPLUNK® IT SERVICE INTELLIGENCE™) toidentify when the values of data such as a KPI reflect anomalousbehavior (e.g., an occurrence that is relatively less predictable and/ormore surprising than previously received/identified KPI values). Thatis, it can be appreciated that in certain implementations definingand/or applying static thresholds to data such as KPI values (e.g., inorder to identify KPI values that lie above and/or below suchthresholds) may be effective in enabling the identification of unusualbehavior, occurrences, etc. In certain circumstances, however, suchthresholds may not necessarily identify anomalous behavior/occurrences,such as with respect to the deviation and/or departure of particulardata such as a KPI value from a trend that has been observed/identifiedwith respect to prior data values, as is described herein. For example,certain machine behavior, occurrences, etc. (e.g., as reflected in oneor more KPI values) may not necessarily lie above or below a particularthreshold. However, upon considering a current data (e.g., KPI values)in view of various trend(s) identified/observed in prior data values(e.g., training data such as historical KPI values, simulated KPIvalues, etc.), the current value, may nevertheless reflect anomalousbehavior/occurrences (in that the current data (e.g., KPI) value, forexample, deviates/departs from the identified trend).

It should be understood that while in certain implementations thereferenced anomalies may correspond to behavior or occurrences asreflected in data (e.g., KPI) values that may be greater or lesser thanan expected/predicted data (e.g., KPI) value (as described in detailbelow), in other implementations such anomalies may correspond to theabsence or lack of certain behaviors/occurrences. For example, in ascenario in which certain data (e.g., KPI) values have beenobserved/determined to demonstrate some amount of volatility, uponfurther observing/determining that subsequent data (e.g., KPI) valuesare relatively less volatile, such behavior/occurrence can also beidentified as anomalous (despite the fact that the data (e.g., KPI)value(s) do not fall above or below a particular threshold).

In an embodiment, FIG. 5 illustrates an exemplary GUI 500, in accordancewith one or more embodiments of the present disclosure. It should beunderstood that GUI 500 (as depicted in FIG. 5) corresponds to aparticular KPI (here, ‘ABC KPI 2’), though in other implementations sucha GUI may correspond to any other type of data, multiple data categories(e.g., KPIs), an aggregate or composite of data (e.g., KPI), etc. (e.g.,for a cohesive anomaly detector that monitors a number of KPIs toidentify changes in data between multiple KPIs). GUI 500 may includeactivation control 502 and data window selector 504. In an embodiment,activation control 502 can be, for example, a button or any other suchselectable element or interface item that, upon selection (e.g., by auser), enables and/or otherwise activates the various anomaly detectiontechnologies described herein (e.g., with respect to a particular KPI orKPIs). In an embodiment, upon activating anomaly detection viaactivation control 502, data window selector 504 and other userinterface elements (not depicted) can be presented to the user via GUI500.

In an embodiment, data window selector 504 can enable the user to definea window (e.g., a duration, number of data points, or time range) ofdata (e.g., KPI) to provide as a signal (e.g., a sequential set of datapoints) that will be used to perform anomaly detection. Different datamay arrive from different sources and may be stored at differentintervals (e.g., resulting in different resolutions). For each datacategory (e.g., KPI), an anomaly detection definition may have its ownsignal that is stored within a data queue. In an embodiment, by definingthe data window that may be used for the anomaly detection definitionassociated with the particular data (e.g., KPI), the frequency withwhich data points may be provided to the signal (e.g., an intervalbetween data points) may be determined, for example, based on theduration of the data defined by the data window selector and the numberof data points that are available in a data queue for the anomalydetection definition. In some embodiments, a data queue size for theanomaly detection definition may be modified to accommodate differentdata window selections.

Although not depicted in FIG. 5, in some embodiments a selection input(e.g., a pull-down menu, radio button, etc.) may be provided to selectbetween available anomaly detection procedures. Although any suitableanomaly detection procedure may be used for any suitable data source, inan embodiment, available anomaly detection procedures may include atrending anomaly detection procedure, a cohesive anomaly detectionprocedure, and a sparse anomaly detection procedure. In an embodiment,performing any anomaly detection procedure may provide an output such asan anomaly result. An anomaly result may be an output of the anomalydetection procedure, such as an anomaly value, an anomaly score, ananomaly definition, or an anomaly alert.

In an embodiment, a trending anomaly detection procedure may provide foranalysis of anomalies within a single KPI over time, e.g., by comparingdata points within a single signal for a single anomaly detectiondefinition with other data points of the same signal. Trending anomalydetection may be performed on the data to determine whether any points(or set of points) within the sequential set of data points of thesignal correspond to an anomaly. In this manner, a trending anomalydetection analysis may analyze not only the most recent data point orset of data points, but may continuously determine whether prior datapoints correspond to an anomaly based on the sequential set of datapoints of the signal that is currently within the data queue. In anembodiment, a sparse algorithm may operate on a single KPI in a similarmanner to a trending algorithm, but may be optimized for sparse datasets that have few data points, for example by utilizing additionalhistorical data points if the existing sequential set of data points forthe data detection window for a signal is inadequate to perform anomalydetection.

In an embodiment, a cohesive anomaly detection procedure may analyzedata from multiple KPIs as a cohesive detection group in order toidentify whether one of the KPIs is functioning differently from theother KPIs of the cohesive detection group. Cohesive detection groupsmay be selected in any suitable manner, such as by a user selection(e.g., identifying data (e.g., KPIs) to analyze as a cohesive detectiongroup from a user interface (not depicted)), automatically based on data(e.g., KPIs) that exhibit common trends over time, and based on a hybridinterface that allows for user selections among data (e.g., KPIs) thatare automatically identified. Data points from the data (e.g., KPIs) inthe cohesive detection group may be compared between data categories(e.g., KPIs), and anomalies may be detected when the comparativebehavior of the data categories (e.g., KPIs) to each other (e.g.,determined as an anomaly result such as anomaly scores) differs from thecomparative behavior at other points within the sequential set of datafor the data categories (e.g., KPIs). In an embodiment, the system mayactively monitor anomaly detection definitions for data categories(e.g., KPIs) to identify data categories (e.g., KPIs) that arecorrelated, generate cohesive detection groups based on the monitoring,and identify anomalies for these cohesive detection groups.

Although anomaly detection may be determined in a variety of manners, inan exemplary embodiment the signal for each anomaly detection definitionmay be periodically analyzed as the data within the signal changes(e.g., based on new data points for the KPI being inserted into thesignal and older data points being removed). In an exemplary embodiment,the signal (e.g., the entire sequential set of data points or someportion thereof) may be pre-processed, anomaly scores may be calculatedfor the signal, and the anomaly scores may be compared to one or morethresholds in order to determine whether an anomaly has occurred andwhat types of alerts should be provided in response to a detectedanomaly.

In an embodiment, pre-processing may include any suitable processing forthe signal, such as determining an analysis window, normalizing datapoints, resampling and/or interpolating data points, any other suitablepre-processing, or any combination thereof. Pre-processing may result indata points that are suitable for anomaly scoring, such as by modifyingthe resolution, magnitude, or other characteristics of the data pointsfor the anomaly scoring algorithm. For a cohesive anomaly definition(e.g., an anomaly definition in which multiple KPIs are analyzed againsteach other), the data points associated with each data category (e.g.,KPI) may be applied to a similar magnitude scale, a trend may bedetermined for each data category (e.g., KPI) (e.g., based on a rollingmedian), the noise in the data may be determined from the raw data andthe trend, and the normalized data may be determined based on the noiseand the trend.

In an embodiment, anomaly scoring may be determined based on a varietyof statistical techniques, such as behavior modeling (e.g., using modelslike Holt-Winters or ARIMA), statistical distribution p-testing,non-parametric distribution comparison (e.g., Kullback-Leibler), ornon-parametric distance functions (e.g. L1/Manhattan distance). Foranomaly scoring for a trending-type anomaly detection definition, thedata points are analyzed to determine the degree to which data pointsdeviate from the signal under analysis. For anomaly scoring of acohesive anomaly detection definition, the data points for each of thedata categories (e.g., KPIs) may be compared to each other and analyzedbased on the overall patterns of differences between the data points forthe respective data categories (e.g., KPIs).

In an embodiment, determination of anomaly thresholds, analysis of thosethresholds, and determinations of alerts may be performed based on ananalysis of the signal as well as user inputs such as sensitivitysettings. In some embodiments, a base threshold may be determined basedon statistical techniques, such as by determining standard deviationsbetween data points, determining a discrete gradient for the standarddeviations, and setting a threshold based in part on the discretegradient. In some embodiments, the threshold may be adjusted based on auser input such as sensitivity. Anomalies may be detected based oncomparison of anomaly scores with the anomaly threshold, and alerts maybe generated based on the comparison and alert settings.

FIG. 6 illustrates an exemplary GUI 600 in accordance with one or moreembodiments of the present disclosure. Although GUI 600 may include anysuitable user interface elements, in an embodiment GUI 600 may includesearch preview selector control 602, sensitivity setting indicator 604,sensitivity setting control 606, alert setting control 608, searchpreview window 610, and data selection 612. Search preview selectorcontrol 602 can be, for example, a drop down menu or any other suchselectable element or interface item that, upon selection (e.g., by auser) enables a user to define or select a chronological interval withrespect to those anomaly scores (and their corresponding data (e.g.,KPI) values) that have been identified as anomalies are to be presented(e.g., within search preview window 610), as described herein.

In an embodiment, sensitivity setting control 606 can be, for example, aselectable element (e.g., a movable slider, a pull-down menu, or anumerical text input) or interface item that, upon selection (e.g., by auser), enables a user to select or define a setting that dictates thesensitivity (e.g., between ‘1,’ corresponding to a relatively lowsensitivity and ‘100,’ corresponding to a relatively high sensitivity,the presently selected value of which is reflected in sensitivitysetting indicator 604) with respect to which anomaly scores associatedwith data (e.g., KPI) values are to be identified as anomalies. That is,in an embodiment, as described herein, an anomaly value may becalculated for some or all data points within a sequential set of datapoints of a signal that is used for anomaly detection. In an embodiment,the sensitivity setting indicator may be utilized to establishthresholds for anomaly scores that will be identified as an anomaly.Accordingly, the referenced sensitivity setting can dictate/define ananomaly threshold which can be, for example, a threshold by which suchdeviations are to be considered/identified as anomalies. For example, asensitivity setting of ‘10’ may correspond to the 10th percentile of thereferenced deviations from historical anomaly scores. Accordingly, basedon such a selection, all those anomaly scores that are above the 10thpercentile with respect to their deviation from the non-anomalous datapoints within the signal would be identified as anomalies. By way offurther example, a sensitivity setting of ‘99’ may correspond to the99th percentile of the referenced deviations from the other data pointswithin the signal. Accordingly, based on such a selection, only thoseanomaly scores that are above the 99th percentile with respect to theirdeviation from other data points would be identified as anomalies.

In an embodiment, providing the referenced sensitivity setting control606, the described technologies can enable a user to adjust thesensitivity setting (thereby setting a higher or lower error thresholdwith respect to which anomaly scores are or are not identified asanomalies) and to be presented with real-time feedback (via searchpreview window 610) reflecting the underlying data such as anomalyscores or underlying data (e.g., KPI) values below. An exemplary anomalydetection preview for a particular signal is depicted in search previewwindow 610, with anomaly scores values scaled along the ordinate of thesearch preview window 610 and anomaly scored depicted versus time (e.g.,along the abscissa of the search preview window 610). In an embodiment,a depiction of an anomaly score threshold and data points of the signalthat fall outside of that threshold are depicted as a dashed line and aspoints above that dashed line, respectively.

In an embodiment, alert setting control 608 can be, for example, aselectable button, checkbox, etc., or any other such selectable elementor interface item that, upon selection (e.g., by a user) enables a userto select or define whether or not various alerts, notifications, etc.(e.g., email alerts, notable events, etc.), are to be generated and/orprovided, e.g., upon identification of various anomalies. Although notdepicted in FIG. 6, once an alert setting control is selected, a varietyof user interfaces may be provided to customize alerts, e.g., based ontypes of alerts, recipients, contents of alerts, severity thresholds fordifferent types of alerts, etc.

In an embodiment data selection 612 may provide user interface elementsfor selecting particular additional data to monitor with the anomaly(e.g., based on selections from a search window, pull-down menu, orselection boxes) and for automatically identifying data to monitor withan anomaly. In some embodiments, in addition to identifying an anomalyfor related data, the system may also identify other data (e.g., metricdata, KPI data, raw machine data) from the data (e.g., KPI) system orfrom other data sources or systems, that relates to an identifiedanomaly. In an embodiment, when an anomaly is identified, particulardata may be searched (e.g., based on selected data) to determine if itis correlated to the anomaly, or such search may automatically beperformed for a subset of data (e.g., based on selecting “Auto” fromdata selection 612. In this manner, it may be possible to identify theimpact that a particular anomaly has on the operation of the monitoredsystem (e.g., an IT system).

FIG. 7 illustrates an exemplary GUI 700 for monitoring in accordancewith one or more embodiments of the present disclosure. In anembodiment, GUI 700 may include search preview window 610 (as describedwith respect to FIG. 6), KPI value graph 702, anomaly point(s) 704,anomaly information 706, alert management control 708, and related datadisplay 710. In the exemplary embodiment of FIG. 7, the values utilizedfor the ordinate of the search preview window may be data (e.g., KPI)values (compared to anomaly scores, as depicted in FIG. 6) such that thevalue graph is a KPI value graph 702 (compared to the anomaly scorevalue graph of FIG. 6). KPI value graph 702 can be, for example, a graphthat depicts or represents KPI values (e.g., ‘CPU usage’) over thechronological interval defined by search preview selector control 602(e.g., the past 24 hours). It should be understood that, in certainimplementations, the referenced chronological interval may be adjusted(e.g., zoomed-in, zoomed-out) by the user, e.g., at run time (such as byproviding an input via search preview selector control 602). In doingso, only a portion of the chronological interval may be displayed insearch preview window 610, or alternatively, an additional time periodcan be added to the chronological interval, and the resulting extendedchronological interval can be displayed in search preview window 610. Inan embodiment, anomaly point(s) 704 can be visual identifiers (e.g.,highlighted or emphasized points or graphical indicators) depicted alongthe graph. The placement of such anomaly points 704 within searchpreview window 610 can reflect the point in time in which the underlyingdata (e.g., KPI) (with respect to which the anomaly was detected)occurred within the chronological interval (e.g., the past 24 hours).For example, the left-most area of search preview window 610 cancorrespond to the beginning of the referenced 24-hour period while theright-most area of search preview window 610 can correspond to the endof the referenced 24-hour period.

As described above, in an embodiment, the anomaly point(s) 704 that aredisplayed along KPI value graph 702 are identified based on thesensitivity setting provided by the user (via sensitivity settingcontrol 604). Accordingly, as the user drags the slider (that is,sensitivity setting control 604) towards the left, thereby lowering thesensitivity setting (that is, the error threshold by which anomalyscores are to be determined to be anomalies with respect to theirdeviation from historical anomaly scores for the data (e.g., KPI)),relatively more anomalies are likely to be identified. Conversely, asthe user drags the slider (that is, sensitivity setting control 606)towards the right, thereby raising the sensitivity setting (that is, theerror threshold by which anomaly scores are to be determined to beanomalies with respect to their deviation from historical anomaly scoresfor the data (e.g., KPI)), relatively fewer anomalies are likely to beidentified. In doing so, the user can actively adjust the sensitivitysetting via sensitivity setting control 606 and be presented withimmediate visual feedback regarding anomalies that are identified basedon the provided sensitivity setting.

In an embodiment, anomaly information 706 can be a dialog box or anyother such content presentation element within which further informationcan be displayed, such as with respect to a particular anomaly. That is,having identified various anomalies (as depicted with respect to anomalypoints 704), it may be useful for the user to review additionalinformation with respect to the identified anomalies. Accordingly, uponselecting (e.g., clicking on) and/or otherwise interacting with (e.g.,hovering over) a particular anomaly point 704, anomaly information 706can be presented to the user. In certain implementations, such anomalyinformation 706 can include the underlying data (e.g., KPI) value(s)associated with the anomaly, the anomaly score, a timestamp associatedwith the anomaly (reflecting, for example, the time at which the KPI hadan anomalous value), and/or any other such underlying information thatmay be relevant to the anomaly, KPI, etc. In doing so, the user canimmediately review and identify information that may be relevant todiagnosing/identifying and/or treating the cause of the anomaly, ifnecessary.

It should also be noted that, in certain implementations, the referencedanomaly information 706 dialog box (and/or one or more elements of GUI700) can enable a user to provide various types of feedback with respectto various anomalies that have been identified and/or presented (as wellas information associated with such anomalies). Examples of suchfeedback that a user may provide include but are not limited to feedbackreflecting that: the identified anomaly is not an anomaly, theidentified anomaly is an anomaly, an anomaly score/corresponding data(e.g., KPI) value that was not identified as an anomaly should have beenidentified as an anomaly, an anomaly score/corresponding data (e.g.,KPI) value that was not identified as an anomaly is, indeed, not ananomaly, the identified anomaly is not as anomalous as reflected by itscorresponding anomaly score, the identified anomaly is more anomalousthan is reflected by its corresponding anomaly score, the identifiedanomaly together with one or more nearby (e.g., chronologicallyproximate) anomalies are part of the same anomalous event, theidentified anomaly is actually two or more distinct anomalies, etc. incertain implementations, the referenced feedback may originate from amultitude of sources (similar to the different sources of training datadescribed herein). For example, labeled examples of anomalies andnon-anomalies can be gathered from similar but distinct systems or fromcommunal databases.

It should be further noted that while in certain implementations (suchas those described herein) the referenced feedback can be solicitedand/or received after an initial attempt has been made with respect toidentifying anomalies, in other implementations the describedtechnologies can be configured such that a training phase can first beinitiated, such as where a user is presented with some simulated orhypothetical anomalies with respect to which the user can provide thevarious types of feedback referenced above. Such feedback can then beanalyzed/processed to gauge the user's sensitivity and/or to identifywhat types of anomalies are (or aren't) of interest to them. Then, uponcompleting the referenced training phase, a detection phase can beinitiated (e.g., by applying the referenced techniques to actual data(e.g., KPI)values, etc.). Moreover, in certain implementations thedescribed technologies can be configured to switch between training anddetection modes/phases (e.g., periodically, following some conditionaltrigger such as a string of negative user feedback, etc.).

Moreover, in certain implementations the described technologies can beconfigured to detect/identify anomalies in/with respect to differentapplications. For example, it can be appreciated that with respect todifferent user roles, e.g., an IT manager and a security analyst,anomalies identified in one application may not be considered anomaliesin another application. Thus, depending on, for example, the role of theuser, different anomalies may be identified. In certain implementations,the feedback provided via the slider and/or one of the mechanismsdescribed above can further impact the active application or some subsetof applications (but not other(s)).

In an embodiment, alert management control 708 can be, for example, aselectable element or interface item that, upon selection (e.g., by auser), enables a user to further manage various aspects of alerts,notifications, etc. (e.g., email alerts, notable events, etc., as aredescribed herein) that are to be generated and/or provided, e.g., uponidentification of various anomalies.

In an embodiment, related data 710 may provide a display of data that isassociated with an anomaly. As described herein, at data selection 612 auser may select data to monitor along with an anomaly detectiondefinition, and in some embodiments, may cause the system toautomatically determine other data associated with an anomaly. Relateddata 710 display may provide a depiction of this related data. In anembodiment, the related data 710 may include values (e.g., KPI values)and may provide visual indicators (e.g., coloring or shading) based onthresholds or other comparison values. The display may correspond to apoint of interest for the KPI value graph (e.g., based on a userselecting a point or hovering a cursor over a point).

FIG. 8 is a flow diagram depicting exemplary steps 800 for anomalydetection in accordance with one or more embodiments of the presentdisclosure. Method 800 may be performed by processing logic that maycomprise hardware (circuitry, dedicated logic, etc.), software (such asthe one run on a general purpose computer system or a dedicatedmachine), or a combination of both. In one implementation, the method800 may be performed by a client computing machine. In anotherimplementation, the method 800 may be performed by a server computingmachine coupled to the client computing machine over one or morenetworks.

Although the steps of FIG. 8 are generally described in the context ofan anomaly detector for KPI data, it will be understood that they mayapply equally to other anomaly detection applications based on otherdata types. The steps depicted by FIG. 8 are provided for illustrativepurposes only; those skilled in the art will understand that additionalsteps may be included, that one or more steps may be removed, and thatthe ordering of the steps of FIG. 8 may be modified in any suitablemanner. It will be understood that while particular hardware, software,system components, search techniques, and anomaly detection proceduresmay be described in the context of FIG. 8, that the steps describedherein are not so limited.

Method 800 may begin at block 802 when the computing machine may executea search query, such as over a period of time. In certainimplementations, the referenced search query can be executed repeatedly,such as over a period of time and/or based on a frequency and/or aschedule. In doing so, values for a key performance indicator (KPI) canbe produced. In certain implementations, such a search query can definethe KPI. The referenced search query can derive a KPI value indicativeof the performance of a service at a point in time or during a period oftime. Such a value can, for example, be derived from machine data, suchas machine data pertaining to one or more entities that provide theservice, as is described herein. In certain implementations, suchmachine data may be produced by two or more sources. Additionally, incertain implementations, such machine data may be produced by anotherentity. Moreover, in certain implementations, such machine data may bestored as timestamped events (each of which may include a segment of rawmachine data). Such machine data may also be accessed according to alate-binding schema. Once a KPI is identified for a search query, andother data related to anomaly detection for a KPI is provided (e.g., adata window), a signal may be acquired for the KPI as described hereinand an anomaly definition may be created.

At block 804, a graphical user interface (GUI) enabling a user toindicate settings for anomaly detection definition of the KPI, such as asensitivity setting and related data settings. For example, as describedherein with respect to FIGS. 5-7, upon activating activation control502, a sensitivity setting control 606 and a data selection control 612can be displayed. As described above, sensitivity setting control 606can enable a user to define an error threshold above which, for example,a computed anomaly score (which corresponds to one or more underlyingKPI values) is to be identified as an anomaly (and below which such anerror is not to be identified as an anomaly). In some implementations,sensitivity setting control 606 can be a slider. Data selection control612 can allow for a selection of particular related data to monitor, aswell as the enablement of automatic detection of other related data thatmay be determined to be correlated or otherwise related to anomalies forthe KPI at issue.

At block 806, the user inputs can be received. In certainimplementations, such user input can be received via the GUI (e.g.,sensitivity setting control 606 and data selection setting 612).Moreover, in certain implementations, such input can indicate thesensitivity setting desired by the user (e.g., an error threshold abovewhich a computed anomaly score is to be identified as an anomaly andbelow which such an error is not to be identified as an anomaly). Insome implementations, the user input can be received when the user movesthe slider to a certain position. As described herein, the dataselection setting may include identifying related data via a search,selection box, or pull down, as well as selection of automaticmonitoring.

At block 808, zero or more of the values can be identified as anomalies.In certain implementations, such values can be identified as anomaliesbased on the settings for the anomaly detection definition, such as asensitivity setting indicated by user input (e.g., via sensitivitysetting control 606), a data window for the anomaly definition, theanomaly detection procedure for the anomaly definition, and any othersuitable inputs.

At block 810, a GUI that includes information related to the valuesidentified as anomalies may be provided. In certain implementations, theinformation related to the values identified as anomalies can includeinformation such as an anomaly value graph, KPI value graph, detailedanomaly information, a count of the anomalies, related data information,and other suitable information related to the presence orcharacteristics of an anomaly. For example, a display of a graph thatincludes information related to any values identified as anomalies canbe adjusted. In certain implementations, such a display can be adjustedbased on the user input indicating the sensitivity setting. For example,as described in detail with respect to FIGS. 5-7, upon receiving varioussensitivity setting inputs via sensitivity setting control 606,automatic (without any user input other than the sensitivity settinginput) identification of anomalies can be repeated and the graph asdisplayed in search preview window 610 can be dynamically adjusted,e.g., with respect to the quantity, position, etc., of various anomalypoints 704 (and their corresponding information). Related data candisplay information such as scores, thresholds, and visual indicators.

At block 812, an alert can be generated. The alert may be generatedbased on the identified anomalies and the alert settings provided by auser (e.g., based on alert setting control 608 and alert managementcontrol 708).

3.2. Continuous Anomaly Detection

In some embodiments, the anomaly detection service may be implemented asa continuous anomaly detection service. As described herein, continuousanomaly detection can be applied to a number of incoming data streamsthat may include real-time or near real-time data provided from datasources such as components of an IT system. In some embodiments,processing may have been applied to the data streams prior to beingprovided as data streams to the continuous anomaly detection search.Exemplary processing that may be applied include any suitable portion ofindexing and KPI processing as described herein that is performed priorto storage in a data store. Thus, rather than accessing a portion ofdata points from a data store each time an anomaly detection analysis isperformed, and analyzing the accessed data points, a plurality ofsignals may be continuously generated and stored for each KPI that is tobe analyzed by the anomaly detector, based on data points that are mostrecently received from the data streams. Anomaly detection iscontinuously performed on this most recently received data, e.g., byperforming anomaly detection on the most recently received data pointsbased on the other data points of the signal. In an embodiment, as datapoints continue to be provided from the incoming data streams, each ofthe signals may be updated with data points that correspond to theparticular KPI, with earlier data points that now fall outside of a datawindow under analysis being removed from the sequential set of datapoints of the signal. Each signal may then persist and be continuouslyupdated as new data points are received through the continuous inputfrom incoming data streams. Anomaly detection may be performedcontinuously with each update of most recently received data points. Anexample of such anomaly detection is provided in FIG. 9, which depictsexemplary continuous anomaly detection in accordance with someembodiments of the present disclosure.

As is depicted in FIG. 9, in an embodiment, inputs for anomaly detectionmay include a plurality of data streams 904 provided by a plurality ofdata sources 902 ₁-902 _(N). Each data source may provide numerous datastreams 904 (e.g., tens, hundreds, or thousands) representing differentaspects of data that is provided by the data source to a data intake andquery system. In some embodiments, the data streams may representinformation relating to the operation of an IT system as describedherein, and may be provided periodically or in some embodiments, in realtime, such that in most instances the data of a received data stream isprovided in the order that the underlying data is created.

In some embodiments historical data 908 from a data store 906 may beused for purposes of providing historical data for a signal. Historicaldata 908 may correspond to a lengthy storage of historical data in datastore 906 (e.g., such as a data intake and storage system), which maytypically persist indefinitely unless data is intentionally deleted.Historical data 908 may be accessed for a variety of purposes to assistin anomaly detection, such as to pre-load or backfill data points intothe signals.

In an exemplary embodiment of pre-loading, when an anomaly definition isinitially configured, it may be desired to access a prior store of data(e.g., historical data 908) to establish the necessary number of thesequential set of data points in the first instance, rather than waitingfor the amount of time it would take for the necessary amount of data tobe established from incoming data streams 904 (i.e., based on each datapoint of a data stream being received by the signal at a certaininterval, until a necessary number of data points for anomaly detectionof the signal is received). In an embodiment, the historical data 908may be provided as data points for the signal, in an order such that themost recent data points are provided at the beginning of the signal(e.g., at the position within the signal that new data points from adata stream 904 will be received). In an embodiment, a number of datapoints of historical data 908 may be accessed and the historical datamay be sequenced and reordered prior to providing the historical data908 as the sequential set of data points, Once the necessary number ofdata points (e.g., a number of data points necessary to fill a signal,or a lesser number of data points required to perform anomaly detection)for a signal are received as historical data 908 from the data store,the signal can begin to be populated with newly received data points ofa data stream 904 from the data sources 902 ₁-902 _(N).

In an exemplary embodiment of backfilling, it may be determined that thedata within an existing signal is incomplete (e.g., as a result oftransmission or receiving errors of the data being provided by the datastream 904) or that a change to the signal is required (e.g., due to achange in the anomaly detection configuration). Because the same datastreams are also being provided for storage at data store 906, any suchmissing, corrupted, aberrant, or changed data may be remedied orreplaced based on accessed stored data. In an embodiment of replacingdata points of a signal, target data points within the signal may beidentified for replacement and replaced by historical data points.

In an embodiment, signals may be established and updated based on ananomaly detector search command 910. The anomaly detector search commandmay perform searches on incoming data streams 904 based on anomalydetection configurations provided for each of a plurality of anomalydetection definitions. In an embodiment, an anomaly detectionconfiguration of an anomaly detection definition may provide informationthat is necessary to establish and configure the sequential set of datapoints of a signal (or in the case of a cohesive anomaly detectionprocedure, a plurality of signals), update signals based on incomingdata streams 904, perform pre-loading or backfilling of signal based onhistorical data 908, dictate anomaly detection procedures associatedwith the anomaly detection definition and one or more signals, provideconfiguration parameters for the signals and anomaly detectionprocedures (e.g., data window length, resolution, algorithms,thresholds, sensitivity, and alerts), and any other suitable informationrelating to a definition. In an embodiment, the anomaly detectionconfigurations may have a common data structure. The common datastructure may allow for the anomaly detection configurations to beaccessed, implemented, invoked, and updated in a similar manner.Exemplary elements of the common data structure may include commonconfiguration parameters, common scaling, common storage, and commonnaming conventions.

In an embodiment, anomaly detection search command 910 may be applied tothe incoming data streams 904 in order to extract data points for thesignals of the anomaly detection system. In an embodiment, a searchcommand may be generated based on the types of data that are requiredfor the signals by the anomaly detection definitions, based on theanomaly detection configurations. The search may be run on a regularbasis (e.g., periodically), relevant data signals may be identified fromthe plurality of received data signals based on information associatedwith the data stream (e.g., KPIs associated with an anomaly detectionconfiguration that correspond to the information of a data signal orsignals), a new data point or new data points may be extracted from eachdata stream that is associated with a signal, and the signal may beupdated based on the new data point or data points. If, as describedherein, a data queue associated with a signal is full, a correspondingnumber of data points (e.g., the oldest data points in the sequentialset of data points of the signal) may be removed from the signal. Theanomaly detection search command 910 may be run as a single searchcommand including parameters for searching all of the incoming datastreams, or in some embodiments, as a plurality of search commands(e.g., for different data sources 902 ₁-902 _(N), different KPI types,different data windows, different data frequencies, different anomalydetection procedures, etc.).

An exemplary invocation of a search command may be “ . . . |madcontext=context_a| . . . ”, which may provide an indication that the “ADService” (mad command) should start and use all of the signal andalgorithm configurations associated with the “AD Service Context” named“context_a”. An exemplary full search (e.g., a SPL search) using the madcommand may be a search such as “index=metric_index|madcontext=context_a|collect index=ad_output”, in which“index=metric_index” is a base search to select a set of search results(e.g., events from a Splunk search) containing metric data to operateon, in which “|mad context=context_a|” is the invocation of thecontinuous anomaly detection service for a specific configurationcontext, and in which “|collect index=ad_output|” instructs the systemto save the output of the continuous anomaly detection service into aseparate index “ad_output”

In an embodiment, the result of the anomaly detection search command 910may be data points extracted from the incoming data streams, eachdirected at particular signals 912 ₁-912 _(M). Although any suitabledata may be represented within signals 912 ₁-912 _(M), in an embodiment,each of the signals 912 ₁-912 _(M) may be associated with a KPI, e.g.,KPI₁-KPI_(M). In this manner, the anomaly search command may bestructured in a manner that allows for simplified searching of theincoming signal stream 904, e.g., based on established KPIs that asignal may be associated with. The relationship between a KPI (e.g.,KPI₁-KPI_(M)) and a signal (e.g., 912 ₁-912 _(M)) may be established andstored as anomaly detection configuration information for an anomalydetection definition.

In an embodiment, each signal 912 ₁-912 _(M) may be established andrefreshed based on the anomaly detection configuration of the anomalydetection definition associated with the signal. As described herein,the anomaly detection configuration may define signal parameters such asa data window, refresh rate, data point frequency, resolution, datascaling, and other relevant information that defines the manner thatdata is stored in a particular signal. Signals 912 ₁-912 _(M) may havethe same or varied storage capacity based on system settings, anomalydetection configurations, and data point sizes. In one embodiment, eachsignal may be assigned a particular amount of memory for storing itssequential set of data points. Although the memory may be operated asany suitable data structure in which the data may be properly ordered(e.g., FIFO, LIFO, push and pop, etc.), in an embodiment the memory mayoperate as a FIFO (e.g., circular) queue, with newest data pointsreplacing oldest data points within the sequential set of data points,and all of the data points being stored sequentially (e.g., based on apointer identifying the start (most recent) point in the circularqueue).

In an embodiment, the anomaly detection configuration for an anomalydetection definition may also provide information regarding the anomalydetection procedure that will be implemented by each anomaly detectiondefinition. In FIG. 9, a plurality of trending anomaly detectiondefinitions are depicted as 914 ₁-914 _(X), and are each associated witha single signal. Although a trending anomaly detection definition 914₁-914 _(X) is depicted as associated with every signal 912 ₁-912 _(M) inFIG. 9, it is not necessary that every signal 912 ₁-912 _(M) beassociated with an anomaly detection definition. For example, somesignals may only be established for purposes of cohesive anomalydetection, e.g., as depicted in FIG. 9 as cohesive anomaly detectiondefinitions 916 ₁-916 _(Y). Thus, each signal 912 ₁-912 _(M) isassociated with at least one anomaly detection definition (e.g.,trending, cohesive, or both). Moreover, each signal may be associatedwith KPIs. In some embodiments an anomaly detection definition mayinclude multiple signals associated with a single KPI. By havingmultiple signals based off a single KPI, different anomaly detectionconfigurations may be used to determine different types of anomalies fora single KPI.

Anomaly detection may be run for a particular anomaly detectiondefinition in a variety of manners. In an embodiment, the anomalydetector search command 910 may also include search strings thatinstruct each anomaly detection definition (e.g., trending anomalydetection definitions 914 ₁-914 _(X) and cohesive anomaly detectiondefinitions 916 ₁-916 _(Y)) to run based on its particular definitionparameters, providing an anomaly result (based on the required anomalydetection procedure and parameters) for each anomaly detectiondefinition. In some embodiments, the command to perform the anomalydetection analysis may be provided at different times, and for differentsignals, e.g., periodically based on timing parameters set in theanomaly detection configuration for each anomaly detection definition orin an ad-hoc manner defined by user commands.

Anomaly detection configurations for anomaly detection definitions mayalso be used to pre-load or backfill data points. In some embodiments,absent an intentional shut down of the anomaly detections definitions ora system error, each of the signals (e.g., signal 912 ₁-912 _(M)) maycontinue to persist as long as the signal has a required minimum amountof data (e.g., based on configuration parameters of an anomaly detectionconfiguration). Individual anomaly detection definitions (e.g., one ormore of trending anomaly detection definitions 914 ₁-914 _(X) andcohesive anomaly detection definitions 916 ₁-916 _(Y)) may be modifiedor deleted automatically (e.g., if data from an incoming data stream isno longer available) or manually (e.g., based on a user input at a userinterface). In an embodiment, when one of the anomaly detectiondefinitions is modified in a manner that requires the deletion of thesignal, or when the entire anomaly detection definition is deleted, theentire signal or signals associated with that anomaly detectiondefinition may be deleted. However, doing so does not impact any othersignal of any other anomaly detection definition, unless two anomalydetection definitions share a single signal (e.g., a trending anomalydetection definition and a cohesive anomaly detection definition beingbased off the same signal). In such a case, the shared signal may beretained for the remaining and unmodified anomaly detection definition.

In an embodiment, when a new anomaly detection definition is created, anew anomaly detection configuration is generated and memory may beidentified or allocated for a new signal associated with the new anomalydetection definition. Before performing anomaly detection on thedefinition, a necessary number of data points must be present within thesignal (e.g., a minimum signal length or the entire signal length). Inan embodiment, rather than waiting for all the incoming data streams toprovide the required number of data points on a going forward basis,data store 906 may be queried in order to acquire historical data 908for the signal. A query for the data store may reference relevantinformation such as relevant KPIs, data intervals, and a starting pointfor the data points. Once the necessary quantity of data points havebeen accessed from the store and stored at appropriate locations withinthe signal, new data points may be provided by the incoming data stream.In this manner, a new signal may be initialized quickly based on data inthe data store, without impacting the operation of the system or anyother signals.

In some embodiments, preliminary anomaly detection results may beprovided as data is provided to the signal, until the required number ofdata points is obtained. It may also be determined in certain instances(e.g., based on a user setting, or analysis of historical data) not toaccess historical data 908 but instead populate the signal only as newdata is received from data streams 904. In such instances, preliminaryanomaly detection results may be provided, with an indication that suchresults are preliminary.

In some embodiments, one or more data points of the signal may bemissing, corrupted, or otherwise unavailable. Because data points aresequential, the points in the sequence where data is missing may beidentified as target data points and a backfill request may be providedto the data store 906. Historical data 908 corresponding to the targetdata points may be reinserted at appropriate locations within thesequential set of data points for the signal. In this manner, the signalmay be repaired without impacting the system as a whole or any othersignals.

3.3. Configuration System for Continuous Anomaly Detection

FIG. 10 is a block diagram depicting an exemplary configuration systemfor anomaly detection in accordance with some embodiments of the presentdisclosure. As described herein, the anomaly detection system mayinclude anomaly detection definitions, each of which has configurationparameters of an anomaly detection configuration. In an embodiment, aconfiguration system may be provided to allow a user to create, modify,and delete anomaly detection definitions. Although a configurationsystem may include any suitable components, in an embodiment theconfiguration system may include an application programming interface(API) 1002 and configuration wrapper 1004. The configuration wrapper1004 may interface with a key value (KV) store 1006 (which may store theunderlying values for the configuration parameters of the anomalydetection configuration), and the anomaly detector module 1008 (whichmay perform anomaly detection based on those configuration parameters).

In an embodiment, the API 1002 may provide an interface for a user tomake requests to the configuration wrapper 1004, which in turn may be alow overhead program operating within the environment of the KV store1006 in order to quickly and easily identify, access, create, delete andmodify information regarding anomaly detection definitions. The API 1002may be any suitable interface that allows a user to communicate with theconfiguration wrapper 1004 to access, modify, delete, and changeinformation about anomaly detection definitions. In an embodiment, API1002 may include a set of commands to allow various standardizedoperations. In some embodiments, an additional interface such as agraphical user interface (e.g., the GUIs of FIGS. 5-7) may be layeredover API 1002 to allow for a user to simply perform the operationsenabled by API 1002 and configuration wrapper 1004.

The API 1002 and configuration wrapper 1004 may provide for a variety ofcommunications regarding anomaly detection definitions. In an exemplaryembodiment as described herein, the communications may be implemented bya REST API having URL-encoded GET arguments or POST parameters, and maybe sent between the API 1002 and configuration wrapper 1004 as JSONmessages. However, it will be understood that an API may be implementedin any suitable manner according to any suitable messaging protocol.Moreover, the configuration parameters for the anomaly detection systemmay be stored and accessed from any suitable data storage location orsystem, and it will be understood that a KV store 1006 is provided as anexemplary embodiment.

One exemplary communication may request a list of anomaly detectioncontexts from the KV store 1006. A context may be configuration objectthat includes one or more anomaly detection definitions and may beassociated with a single anomaly detection search (e.g., the signals andanomaly detection definitions serviced by a single anomaly detectionsearch of the context). A system operating the anomaly detection systemmay include a plurality of contexts, and thus, one request may be a GET“contexts” request that returns the listing of contexts. Another requestrelated to contexts may be a GET “contexts/<context_name>” request thatmay require a name of a desired context and may return the context nameand information about the context if the context exists on the system.

Another exemplary communication related to contexts may be a POST“contexts” request that creates a new context. Exemplary POST parametersfor the POST “contexts” request may be a name of the new context, anidentification of a search (e.g., a search of a set of incoming datastreams, in which the anomaly detection search is implemented) for allof the anomaly detection definitions of the context, a destination foranomaly detection results, whether a saved search is desired, and alocation (e.g., a URL) for the POSTing of alert notifications. A resultmay provide error indications or information about the created context(e.g., name, search, output location of anomaly scores, saved searchindication, and whether the context is disabled).

Another exemplary communication related to contexts may be a POST“contexts/<context_name>” request that modifies an existing context. Thecontext name is the name of the context that will be modified, andexemplary POST parameters for the POST “<contexts_name>” request may bean identification of a search (e.g., a search of set of incoming datastreams, in which the anomaly detection search is implemented) for allof the anomaly detection definitions of the context, a destination foranomaly detection results, whether the context should be disabled, and alocation (e.g., a URL) for the POSTing of alert notifications. A resultmay provide error indications or information about the modified context(e.g., name, search, output location of anomaly scores, saved searchindication, and whether the context is disabled).

Another exemplary communication related to contexts may be a DELETE“contexts/<context_name>” request that deletes the context identified bythe context name. A result may provide error indications or informationabout the deleted context.

Another set of communications may relate to anomaly detectiondefinitions within a particular context. One exemplary communicationrelating to definitions may be a GET“contexts/<contexts_name>/definitions” request that returns the listingof anomaly detection definitions for the context “context_name.”

Another exemplary communication related to definitions may be a GET“contexts/<contexts_name>/definitions/<id>” request that may require aname of a desired anomaly detection definition and may return an erroror information about the anomaly detection definition if it can be foundwithin the context “context_name”.

Another exemplary communication related to contexts may be a POST“contexts/<contexts_name>/definitions” request that creates a newanomaly detection definition. Exemplary POST parameters for the POST“contexts/<contexts_name>/definitions” request may be a JSON object fora field-value map used to select records from the base search, a name ofan anomaly detection procedure to use for the anomaly detectiondefinition, an identification of a JSON object containing configurationparameters for the anomaly detection definition (if not provided, adefault configuration may be used), an indicator of whether the anomalydetection definition is disabled, and a resolution (e.g., time interval)for the signal data of the anomaly detection definition. A result mayprovide error indications or information about the created anomalydetection definition (e.g., id, type of anomaly detection procedure, anidentifier for the JSON objects, resolution, and whether the context isdisabled).

Another exemplary communication related to contexts may be a POST“contexts/<contexts_name>/definitions/<id>” request that modifies theanomaly detection definition identified by the id. Exemplary POSTparameters for the POST “contexts/<contexts_name>/definitions/<id>”request may be a JSON object for a field-value map used to selectrecords from the base search, a name of an anomaly detection procedureto use for the anomaly detection definition, an identification of a JSONobject containing configuration parameters for the definition (if notprovided, a default configuration may be used), an indicator of whetherthe anomaly detection definition is disabled, and a resolution (e.g.,time interval) for the signal data. A result may provide errorindications or information about the modified anomaly detectiondefinition (e.g., id, type of anomaly detection procedure, identifiersJSON objects, resolution, and whether the context is disabled).

Another exemplary communication related to contexts may be a DELETE“contexts/<contexts_name>/definitions/<id>” request that deletes theanomaly detection definition identified by the id. A result may provideerror indications or information about the deleted anomaly detectiondefinition.

Another exemplary communication related to contexts may be a POST“contexts/<contexts_name>/definitions/bulk-delete” request that deletesa number of anomaly detection definition at the same time. In anembodiment, a POST parameter may be an array of anomaly detectiondefinition ids, provided, for example, within a JSON object. A responsemay provide error indications or confirmation of the deleted anomalydetection definitions.

As was discussed above, in some embodiments (e.g., for the creation andmodification of definitions), JSON objects may be provided as elementsprovided in the request. For example, each of the“contexts/<contexts_name>/definitions” and“contexts/<contexts_name>/definitions/<id>” POST requests may include aJSON object that includes field-value map information used to selectrecords from a base search. An exemplary JSON object for providing sucha map is provided below:

{

-   -   type: “simple_selector”, // simple_selector only atm filters:        {// implied AND here with filter attributes        -   <some key>: <some value>        -   . . .

},

-   -   value_key: <key of the value field in record>,        -   [spl_filter: <predicate to search for this metric>]//            OPTIONAL

}

e.g.

{

-   -   “type”: “simple_selector”,    -   “filters”: {    -   “itsi_kpi_id”: “kpi_1”,    -   “itsi_service_id”: “service_1”

},

-   -   “spl_filter”: “indexed_itsi_kpi_id::kpi_1”    -   “value_key”: “alert_value”

}

As another example, each of the “contexts/<contexts_name>/definitions”and “contexts/<contexts_name>/definitions/<id>” POST requests mayinclude a JSON object that includes configuration parameters for ananomaly detection definition. An exemplary JSON for providing suchconfiguration parameters is provided below:

{

“trainingPeriod”: “604800000 ms”,

“maxNAratio”: 0.5,

“currentWindowIx”: “current”,

“trendingNtrend”: 5,

“periodsConfig”: {

-   -   “1 day”: 6,    -   “7 days”: 2

},

“NArm”: true,

“alertConfig”: {

-   -   “Naccum”: 30

},

-   -   “selfComparison”: false,    -   “thresholdConfig”: {        -   “pctOutlier”: 0.2,        -   “slopeThreshold”: 0.4,        -   “diffSigma”: 3.0,        -   “Nkeep”: “180000000 ms”    -   },    -   “windowConfig”: {        -   “windowSize”: 60,        -   “stepSize”: 1

}

}

3.4. Anomaly Detection System

FIG. 11 is a block diagram of an exemplary anomaly detection system inaccordance with some embodiments of the present disclosure. The anomalydetection system may operate on one or more computing units such as oneor more servers, and may include memory for storing executable code toperform the operations described herein and to store data (e.g.,variables, buffers, temporary storage, signals, etc.) as necessary toestablish and store signals, and to perform anomaly detection. Someportions of the system may be implemented at separate servers orhardware, as is useful to optimize the operations of the system.Although the operations depicted and described in in FIG. 11 may beperformed at any suitable time in response to any suitable stimulus orrequest, in an embodiment the operations may performed in response to aperiodic SPLUNK search. In an embodiment, the anomaly detection systemof FIG. 11 may depict a context 1150 having anomaly detectiondefinitions 1132 ₁-1132 _(M). The anomaly detection definitions may havea common type of anomaly detection configurations for the context, whichmay be individually modifiable based on values for individual theanomaly detection configurations.

In an embodiment, an incoming data portion 1102 may be received as achunk of data from the data source such as a data stream (e.g., the datareceived from data sources since the previous chunk of data wasreceived) in response to the search, although in some embodiments, otherdata sources (e.g., a periodic search of data from a data store) may beutilized as the incoming data portion. This data may be accessed by adata management queue such as a chunk turnstile 1104, which may providesome or all of the received incoming data portion 1102 to router 1112.In some embodiments, certain of the data received at chunk turnstile1104 may not be relevant to anomaly detection (e.g., in an exemplaryembodiment, may not be related to a KPI) and may not be included in theanomaly detection chunk 1126 that is provided to the router 1112.

The router 1112 may be in communication with definition manager 1110. Inan embodiment, definition manager 1110 may control the routing of datato anomaly detection definitions 1132 ₁-1132 _(M) based on theconfiguration parameters of the anomaly detection definitions 1132₁-1132 _(M) available at definition manager 1110 (e.g., configurationsfor definitions of context 1150). Definition manager 1110 may receiveanomaly detection configurations 1108 (e.g., from a KV store) forcontext 1150 and based on those anomaly detection configurations 1108and known information about the anomaly detection definitions 1132₁-1132 _(M) (e.g. whether a minimum required number of data points isincluded within the signal), may issue chunk routing requests 1120 torouter 1112 and backfill requests 1122 to backfill manager 1118.

In an embodiment, the chunk routing requests 1120 may provideinformation to identify signals (e.g., a listing of the signals) thatare associated with anomaly detection definitions 1132 ₁-1132 _(M).(e.g., based on KPIs associated with each of the signals or other dataindicators). Based on this information, the router 1112 may identify anymatching data from the anomaly detection chunk 1126, extract thematching data, and transmit one or more signal data chunks 1124 ₁-1124_(M) to each of the anomaly detection definitions 1132 ₁-1132 _(M) forwhich data was received in the anomaly detection chunk 1126. In anembodiment, each respective anomaly detection definition 1132 ₁-1132_(M) may include a reorder buffer 1134 ₁-1134 _(M) for receiving thesignal data chunks. In another exemplary embodiment, the chunk routingrequest 1120 may analyze the underlying data, e.g., to automaticallyidentify data for definitions based on characteristics of the data.

In an embodiment, the backfill request 1122 may provide information toidentify signals (e.g., a listing of signals) for which pre-load orbackfill data is required, as well as information necessary to acquirethe correct data points and amount of data (e.g., data point intervalsfor the signal, start and end times for data points, etc.). Based on thebackfill requests 1122, the backfill manager 1118 may transmit backfillqueries to one or more data stores, and receive backfill responses 1116including the historical pre-load or backfill data. Backfill manager maythen package and route backfill data 1140 ₁-1140 _(M) to anomalydetection definitions 1132 ₁-1132 _(M) as requested by the backfillrequest 1122. In another exemplary embodiment, the backfill request 1122may analyze the underlying data, e.g., to automatically identify datafor definitions based on characteristics of the data.

Although incoming data may be stored and processed in a variety ofmanners, in an embodiment, each of the anomaly detection definitions1132 ₁-1132 _(M) may include memory and processing such as a respectivereorder buffer 1134 ₁-1134 _(M), received data points 1133 ₁-1133 _(M),signal buffer 1136 ₁-1136 _(M), signal data points 1142 ₁-1142 _(M), andanomaly detection procedure 1148 ₁-1148 _(M). Although each anomalydetection definition 1132 ₁-1132 _(M) may have different values forconfiguration parameters (e.g., signal length, data point intervals,anomaly detection procedure, etc.), the types of configurationparameters may be shared for the entire context and the overalloperational flow may be similar for each of the anomaly detectiondefinitions. Accordingly, each of the components of the anomalydetection definitions 1132 ₁-1132 _(M) will be described generically inthe following discussion.

In an embodiment, a reorder buffer 1134 may receive a signal data chunk1124. In some cases, incoming data portions 1102 for a data stream maynot always be provided in chronological order. Incoming data portions1102 may be received relatively frequently (e.g., every 1-5 seconds),and due to processing latency or other causes may occasionally bereceived out of chronological order. Accordingly, a reorder buffer 1134may store the signal data chunks for a longer time than frequency inwhich incoming data portions are received by the system (e.g., 10-60seconds). In an embodiment, the reorder buffer 1134 may place the signaldata chunks in the correct sequence (e.g., based on timestamps) beforeproviding the received data points 1133 to the signal buffer. In otherembodiments (not depicted in FIG. 11), reordering may not be required,and data may be ordered at another time such as at the time that anomalydetection is performed (e.g., based on timestamps of data accessed froma signal).

As described herein, the signal buffer 1136 may also receive backfilldata 1140 (e.g., to fulfill a pre-load or backfill request). In someembodiments, the signal buffer 1136 may order the backfill data 1140 andreceived data points 1133 in sequential order to generate the sequentialset of data points of the signal. As described herein, in an embodimentthe signal buffer 1136 may be a circular queue that replaces the oldestdata points with the most recent data points as incoming received datapoints 1133 are provided to the signal buffer 1136. Some or all of thesequential set of data points stored in the signal buffer may then beprovided as signal data points 1142 to the anomaly detection procedure1148. In an embodiment, anomaly detection may be performed as describedherein, e.g., to determine anomaly detection scores, identify anomaliesfrom those scores, determine information about anomalous data points(e.g., KPI values, etc.), generate alerts, and perform any othersuitable anomaly detection processing.

In an embodiment, the resulting anomaly information 1146 ₁-1146 _(M) maybe provided to an output buffer 1130, which may provide the compiledanomaly data 1128 (e.g., all of the anomaly data generated from onesearch) to the chunk turnstile 1104, which may provide the compiledanomaly data to other components of the system to generate a userinterface and alerts, to store the anomaly data, and to provide otheruser interface, data analysis, and diagnostic functions.

The methods of FIGS. 12-13 depict exemplary steps for initializing,modifying, and operating an anomaly detection system in accordance withsome embodiments of the present disclosure. Although the steps of FIGS.12-13 are generally described in the context of applying particularanomaly detection procedures to KPI data, it will be understood thatthey may apply equally to other anomaly detection procedures and otherunderlying data sources. Moreover, while the steps described herein maybe continuously applied to incoming data streams (e.g., at a regularinterval), it will be understood that signals of anomaly detectiondefinitions may be updated in other manners. The steps depicted by FIGS.12-13 are provided for illustrative purposes only; those skilled in theart will understand that additional steps may be included, that one ormore steps may be removed, and that the ordering of the steps of FIGS.12-13 may be modified in any suitable manner. It will be understood thatwhile particular hardware, software, system components, searchtechniques, and anomaly detection procedures may be described in thecontext of FIGS. 12-13, that the steps described herein are not solimited.

FIG. 12 is a flow diagram depicting exemplary steps for setup andmodification of a continuous anomaly detection system in accordance withsome embodiments of the present disclosure. At step 1202, a user of ananomaly detection system may provide a user input, e.g., to an API 1002.User inputs may include requests relating to contexts, definitions, orother setup and configuration information for the anomaly detectionsystem. In an embodiment, the user input may be provided from the API1002 to the configuration wrapper 1004, which may interact with the KVstore 1006 and anomaly detection module 1008. Processing may thencontinue to step 1204.

At step 1204, the configuration wrapper 1004 may determine whether thereceived request is a request to create a new context of anomalydetection definitions. In an embodiment, the configuration wrapper maydetermine whether the received request relates to a collection ofdefinitions associated with a search (e.g., a context, as indicated by aPOST “contexts” request). If a new context is to be created, processingmay continue to step 1206. If a new context is not to be created,processing may continue to step 1208.

At step 1206, the configuration wrapper 1004 may interact with a storagesystem such as the KV store 1006 and an anomaly detection system such asanomaly detection module 1008 to create the new context. In anembodiment, the new context may be created based on information providedin the POST “contexts” request, such as a name of the new context, anidentification of a search (e.g., a search of set of incoming datastreams, in which the anomaly detection search is implemented), adestination for anomaly detection results, whether a saved search isdesired, a location (e.g., a URL) for the POSTing of alertnotifications, or any other suitable information relating to a singleanomaly detection aspect of a search. After the new context is createdat step 1206, a result may be returned to the API 1002 (includinginformation about the created context such as name, search, outputlocation of anomaly scores, saved search indication, and whether thecontext is disabled) and processing may return to step 1202 to monitorfor additional user inputs.

At step 1208, an interface such as the configuration wrapper 1004 maydetermine whether the received request is a request to modify anexisting context. In an embodiment, the configuration wrapper 1004 maydetermine whether the received request is a POST“contexts/<context_name>” request that identifies an existing context tobe modified. If a context is to be modified, processing may continue tostep 1210. If a context is not to be modified, processing may continueto step 1212.

At step 1210, an interface such as the configuration wrapper 1004 mayinteract with a storage system such as the KV store 1006 and an anomalydetection system such as anomaly detection module 1008 to modify theidentified context. In an embodiment, the context may be modified basedon information provided in the POST “contexts/<context_name>” request,such as an identification of a search (e.g., a search of set of incomingdata streams, in which the anomaly detection search is implemented), adestination for anomaly detection results, whether the context should bedisabled, a location (e.g., a URL) for the POSTing of alertnotifications or any other suitable information relating to a singleanomaly detection aspect of a search. After the new context is modifiedat step 1210, a result may be returned to the API 1002 (includinginformation about the modified context such as name, search, outputlocation of anomaly scores, saved search indication, and whether thecontext is disabled) and processing may return to step 1202 to monitorfor additional user inputs.

At step 1212, an interface such as the configuration wrapper 1004 maydetermine whether the received request is a request to delete anexisting context. In an embodiment, the configuration wrapper maydetermine whether the received request is a DELETE“contexts/<context_name>” request that identifies an existing context tobe deleted. If a context is to be deleted, processing may continue tostep 1214. If a context is not to be deleted, processing may continue tostep 1216.

At step 1214, in an embodiment, an interface such as the configurationwrapper 1004 may interact with a storage system such as the KV store1006 and an anomaly detection system such as anomaly detection module1008 to delete the identified context. After the context is deleted atstep 1214, a result may be returned to the API 1002 (including aconfirmation and information about the deleted context) and processingmay return to step 1202 to monitor for additional user inputs.

At step 1216, an interface such as the configuration wrapper 1004 maydetermine whether the received request is a request to create a newanomaly detection definition. In an embodiment, the configurationwrapper may determine whether the received request is a POST“contexts/<contexts_name>/definitions” request. If a new anomalydetection definition is to be created, processing may continue to step1218. If a new anomaly detection definition is not to be created,processing may continue to step 1222.

At step 1218, an interface such as the configuration wrapper 1004 mayinteract with a storage system such as the KV store 1006 and an anomalydetection system such as anomaly detection module 1008 to establish theanomaly detection procedure. In an embodiment, the anomaly detectionprocedure may be established based on information provided in the POST“contexts/<contexts_name>/definitions” request or a POST“contexts/<contexts_name>/definitions/<id>” request, such as a name ofan anomaly detection procedure to use for the anomaly detectiondefinition, an identification of a JSON object containing configurationparameters for the definition (if not provided, a default configurationmay be used), and an indicator of whether the anomaly detectiondefinition is disabled. Processing may then continue to step 1220.

At step 1220, an interface such as the configuration wrapper 1004 mayinteract with a storage system such as the KV store 1006 and an anomalydetection system such as anomaly detection module 1008 to establish thesignal and backfill the signal with data from a data store. In anembodiment, the information to establish the signal may be based oninformation provided in the POST “contexts/<contexts_name>/definitions”request or a POST “contexts/<contexts_name>/definitions/<id>” request,such as a JSON object for field-value map used to select records fromthe base search and a resolution (e.g., time interval) for the signaldata. Based on this information, the memory (e.g., circular queue forthe signal) for the signal may be established and a pre-load or backfillrequest may be provided to the data store to populate the signal withdata points. Processing may then return to step 1202 to monitor foradditional user inputs.

At step 1222, an interface such as the configuration wrapper 1004 maydetermine whether the received request is a request to modify anexisting anomaly detection definition. In an embodiment, theconfiguration wrapper may determine whether the received request is aPOST “contexts/<contexts_name>/definitions/<id>” request. If an anomalydetection definition is to be modified, processing may continue to step1218. In some embodiments, the existing signal may be deleted and a newsignal and anomaly detection definition may be established in the samemanner as for a newly created anomaly detection definition in steps 1218and 1220. In other embodiments, one or both of steps 1218 and 1220 maybe modified such that existing data points of a signal are reordered andadjusted based on a backfill request, and the anomaly detectiondefinition is retained but modified based on the changed configurationparameters. If the anomaly detection definition is not modified,processing may continue to step 1224.

At step 1224, an interface such as the configuration wrapper 1004 maydetermine whether the received request is a request to delete anexisting anomaly detection definition. In an embodiment, theconfiguration wrapper 1004 may determine whether the received request isa DELETE “contexts/<context_name>/definitions/<id>” request thatidentifies an existing anomaly detection definition to be deleted. If ananomaly detection definition is to be deleted, processing may continueto step 1226. If an anomaly detection definition is not to be deleted,processing may continue to step 1228.

At step 1226, in an embodiment, an interface such as the configurationwrapper 1004 may interact with the a storage system such as the KV store1006 and an anomaly detection system such as anomaly detection module1008 to delete the identified anomaly detection definition. After theanomaly detection definition is deleted at step 1226, a result may bereturned to the API 1002 (including a confirmation and information aboutthe deleted anomaly detection definition) and processing may return tostep 1202 to monitor for additional user inputs.

At step 1228, in an embodiment, an interface such as the configurationwrapper 1004 may interact with a storage system such as the KV store1006 and an anomaly detection system such as anomaly detection module1008 to respond to any other requests. Examples of such requests includeGET “contexts” request (e.g., for querying the configuration wrapper1004 and KV store 1006 for a listing of contexts), a GET“contexts/<context_name>” request (e.g., for querying the configurationwrapper 1004 and KV store 1006 for information about a specificcontext), a GET “contexts/<contexts_name>/definitions” request (e.g.,for querying the configuration wrapper 1004 and KV store 1006 for alisting of anomaly detection definitions), and a GET“contexts/<contexts_name>/definitions/<id>” (e.g., for querying theconfiguration wrapper 1004 and KV store 1006 for information about aspecific anomaly detection definition). Processing may then return tostep 1202 to monitor for additional user inputs.

FIG. 13 is a flow diagram depicting exemplary steps for operating acontinuous anomaly detection system in accordance with some embodimentsof the present disclosure. At step 1302, an incoming data source (e.g.,data streams 904, or data accessed by searching a data store) may bereceived from one or more data sources (e.g., data sources 902 ₁-902_(N)) by the anomaly detection system (e.g., at a chunk turnstile 1104).In an embodiment, data points from the data streams (e.g., anomalydetection chunks) may be provided to a router (e.g., router 1112) as aresult of continuous periodic search. Processing may then continue tostep 1304.

At step 1304, relevant data points may be routed to signals. In anembodiment, a definition manager (e.g., definition manager 1110) mayaccess anomaly detection configurations (e.g., anomaly detectionconfigurations 1108 for anomaly detection definitions 1132 ₁-1132 _(M))for a context in order to provide directions (e.g., chunk routingrequests) for routing the newly received data points to signals (e.g.signals 1136 ₁-1136 _(M) of the anomaly detection definitions 1132₁-1132 _(M)). Each set of data points that is associated with a signalmay be provided to its associated signal (e.g., as signal data chunks1124 ₁-1124 _(M)). Once the data points have been provided to thesignals, processing may continue to step 1306.

At step 1306, the sequential set of data points of each signal thatreceives new data points may be modified based on the newly receiveddata points. In an embodiment of a circular queue, the oldest sequentialdata points may be replaced by the newest sequential data points. Inother queuing systems, the data points may be stored in a differentmanner (e.g., by changing pointers associated with the start and end ofthe memory for this signal). In some embodiments, processing of the newdata points may include reordering the data points (e.g., signal datachunks 1124 ₁-1124 _(M)) in a buffer (e.g., a reorder buffer 1134 ₁-1134_(M)), although, in some embodiments, ordering maybe performed at othertimes such as at the time of anomaly detection. In some embodiments, oneor more of the data points within a signal may be also be updated basedon backfill data (e.g., backfill data 1140 ₁-1140 _(M)), which may beaccessed from a data store (e.g., data store 908) based on a backfillprocedure (e.g., as performed by backfill manager 1118 and definitionmanager 1110). Once the signal data points have been replaced,processing may continue to step 1308.

At step 1308 an anomaly detection procedure may be performed on thesignal data (e.g., by anomaly detection procedures 1148 ₁-1148 _(M)analyzing signal data points 1142 ₁-1142 _(M)). As described herein, avariety of anomaly detection procedures may be applied (e.g., trending,cohesive, or sparse) based on a variety of parameters (e.g., thresholds,sensitivity settings, signal length, alert settings, etc.). In anembodiment, the anomaly detection procedures may determine anomalydetection scores, identify anomalies from those scores, determineinformation about anomalous data points (e.g., KPI values, etc.), andgenerate alerts. Processing may then continue to step 1310. In someembodiments, related data may also be analyzed with the anomalydetection procedure, e.g., based on related data input 612. It may bedetermined whether errors or other changes to the related data arerelated (e.g., correlated) to the determined anomaly.

At step 1310, the anomaly detection results may be delivered to one ormore systems (e.g., via output buffer 1130 and chunk turnstile 1104, asanomaly detection results 1106). In some embodiments, anomaly detectionresults may be provided for storage, for display at a user interface,for further analysis by other computational systems, to alertingsystems, and to various other interfaces that may utilize the anomalydetection results. Processing of steps 1300 may then end.

The foregoing provides illustrative examples of the present disclosure,which are not presented for purposes of limitation. It will beunderstood by a person having ordinary skill in the art that variousmodifications may be made within the scope of the present disclosure. Itwill also be understood that the present disclosure need not take thespecific form explicitly described herein, and the present disclosure isintended to include variations to and modifications thereof, consistentwith the appended claims. It will also be understood that variations ofthe systems, apparatuses, and processes may be made to further optimizethose systems, apparatuses, and processes. The disclosed subject matteris not limited to any single embodiment described herein, but rathershould be construed in breadth and scope in accordance with the appendedclaims.

What is claimed is:
 1. A computer-implemented method for performinganomaly detection, comprising: receiving a plurality of data streams;storing, for each of the data streams, one or more events in a fieldsearchable data store; determining one or more of the data streamsassociated with one or more corresponding signals of a plurality ofsignals; identifying, from the one or more determined data streams,relevant events of the one or more events that are associated with theone or more corresponding signals; identifying, for each of the one ormore determined data streams, a corresponding set of data points byderiving values for the data points from machine data of the relevantevents for the determined data stream; inserting the identified sets ofdata points into the one or more corresponding signals; and continuouslyperforming anomaly detection on the plurality of signals.
 2. Thecomputer-implemented method of claim 1, wherein each of the plurality ofsignals comprises a sequential set of data points, the method furthercomprising: removing, for each of the one or more corresponding signals,a least recently received subset of data points of the sequential set ofdata points from the signal; and updating, for each of the one or morecorresponding signals, the sequential set of data points of the signalby inserting the identified set of data points into a beginning positionof the sequential set of data points, and wherein continuouslyperforming anomaly detection comprises continuously performing anomalydetection for each of the one or more corresponding signals based on theupdated sequential sets of data points.
 3. The computer-implementedmethod of claim 2, wherein, for each of the one or more correspondingsignals, the number of removed data points equals the number of datapoints in the identified set of data points.
 4. The computer-implementedmethod of claim 3, wherein, for each memory location associated with oneof the removed data points, the removed data point is replaced with oneof the updated data points.
 5. The computer-implemented method of claim2, wherein updating the sequential set of data points with the updateddata points comprises: determining a sequential ordering of the updateddata points; and inserting the updated data points into the sequentialset of data points based on the determined sequential ordering.
 6. Thecomputer-implemented method of claim 2, wherein each sequential set ofdata points is stored in a first in first out (FIFO) queue.
 7. Thecomputer-implemented method of claim 6, wherein each FIFO queuecomprises a circular queue.
 8. The computer-implemented method of claim6, wherein, for each sequential set of data points, a pointer defines astarting point for the FIFO queue.
 9. The computer-implemented method ofclaim 1, wherein each of the plurality of signals comprises a sequentialset of data points, and wherein each signal has a required number ofdata points, further comprising: determining, for each signal, whetherthe sequential set of data points has less than the required number ofdata points; and appending, for each of the plurality of signals thathas less than the required number of data points, one or more historicaldata points to the sequential set of data points.
 10. Thecomputer-implemented method of claim 9, wherein appending, for each ofthe plurality of signals that has less than the required number of datapoints, the one or more historical data points to the sequential set ofdata points comprises: determining a number of additional data pointsthat are required for the sequential set of data points to equal therequired number of data points; determining a sequential ordering forthe one or more historical data points within the sequential set of datapoints; accessing the one or more historical data points based on thenumber of additional data points and the sequential ordering; andappending the one or more historical data points to the sequential setof data points based on the sequential ordering.
 11. Thecomputer-implemented method of claim 10, wherein accessing the one ormore historical data points based on the number of additional datapoints and the sequential ordering comprises: requesting the historicaldata points from the field searchable data store based on the number ofadditional data points and the sequential ordering; and receiving thehistorical data points from the field searchable data store.
 12. Thecomputer-implemented method of claim 1, wherein performing anomalydetection comprises performing a cohesive anomaly detection procedure todetermine an anomaly result by: identifying a signal group, wherein thesignal group comprises signals of a subset of the plurality of signalsthat are associated with the cohesive anomaly detection procedure; anddetermining the anomaly result based on a comparison of the signals ofthe signal group.
 13. The computer-implemented method of claim 12,wherein identifying an anomaly based on a comparison of the signals ofthe signal group comprises: identifying, for each of the signals of thesignal group, one or more comparison data points; and determining theanomaly result based on a comparison of the comparison data points ofthe signals of the signal group.
 14. The computer-implemented method ofclaim 1, wherein performing anomaly detection comprises performing atrending anomaly detection procedure to determine an anomaly result by:determining an anomaly detection score based on a changes in data pointsof the one or more corresponding signals over time; and determining theanomaly result based on a comparison of the changes to one or morethresholds.
 15. The computer-implemented method of claim 1, whereindetermining one or more of the data streams associated with one or morecorresponding signals comprises searching each data stream based oncorresponding key performance indicators for the one or morecorresponding signals.
 16. The computer-implemented method of claim 1,further comprising accessing a plurality of anomaly detectionconfigurations, wherein each of the anomaly detection configurationscorresponds to one of the plurality of signals, and wherein each anomalydetection configuration determines a corresponding anomaly detectionprocedure and a plurality of anomaly detection parameters associatedwith the plurality of signals.
 17. The computer-implemented method ofclaim 16, wherein the anomaly detection parameters comprise an anomalydetection threshold, a signal length, or an alert setting.
 18. Thecomputer-implemented method of claim 1, wherein the corresponding set ofdata points is identified by: generating a search command based on ananomaly detection configuration for the one or more correspondingsignals; and periodically executing the search command to extract theset of data points.
 19. A non-transitory computer-readable storagemedium comprising instructions stored thereon, which when executed byone or more processors, cause the one or more processors to performoperations comprising: receiving a plurality of data streams; storing,for each of the data streams, one or more events in a field searchabledata store; determining one or more, for each of the data streamsassociated with one or more corresponding signals of a plurality ofsignals; identifying, from the one or more determined data streams,relevant events of the one or more events that are associated with theone or more corresponding signals; identifying, for each of the one ormore determined data streams, a corresponding set of data points byderiving values for the data points from machine data of the relevantevents for the determined data stream; inserting the identified sets ofdata points into the one or more corresponding signals; and continuouslyperforming anomaly detection on the plurality of signals.
 20. A systemfor performing anomaly detection, comprising: at least one memory havinginstructions stored thereon; and at least one processor configured toexecute the instructions to: receive a plurality of data streams; store,for each of the data streams, one or more events in a field searchabledata store; determine one or more of the data streams associated withone or more corresponding signals of a plurality of signals; identify,from the one or more determined data streams, relevant events of the oneor more events that are associated with the one or more correspondingsignals; identify, for each of the one or more determined data streams,a corresponding set of data points by deriving values for the datapoints from machine data of the relevant events for the determined datastream; insert the identified sets of data points into the one or morecorresponding signals; and continuously perform anomaly detection on theplurality of signals.